public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldv at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/26401] New: Regressons in lchmod and fchmodat when /proc is not mounted
Date: Mon, 17 Aug 2020 16:13:21 +0000 [thread overview]
Message-ID: <bug-26401-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26401
Bug ID: 26401
Summary: Regressons in lchmod and fchmodat when /proc is not
mounted
Product: glibc
Version: 2.32
URL: https://sourceware.org/pipermail/libc-alpha/2020-July/
116512.html
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: ldv at sourceware dot org
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Flags: security-
Fixes for https://sourceware.org/bugzilla/show_bug.cgi?id=14578
introduced regressions in cases when /proc is not mounted:
- lchmod used to return ENOSYS, now it returns EOPNOTSUPP;
- fchmodat(AT_SYMLINK_NOFOLLOW) used to return ENOTSUP, now it returns
EOPNOTSUPP which is different from ENOTSUP on some architectures, e.g. hppa.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-08-17 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 16:13 ldv at sourceware dot org [this message]
2020-08-17 16:14 ` [Bug libc/26401] Regressions " ldv at sourceware dot org
2020-08-25 9:25 ` schwab@linux-m68k.org
2020-10-30 7:31 ` alkisg at gmail dot com
2020-11-04 11:04 ` tom at compton dot nu
2020-11-04 11:09 ` tom at compton dot nu
2020-11-06 16:41 ` arekm at maven dot pl
2021-03-21 10:30 ` sam at gentoo dot org
2022-04-27 12:55 ` adhemerval.zanella at linaro dot org
2022-04-27 13:06 ` ldv at sourceware dot org
2022-04-27 13:36 ` adhemerval.zanella at linaro dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-26401-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).