From: Al Viro <viro@zeniv.linux.org.uk>
To: Rich Felker <dalias@libc.org>
Cc: linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfs: add fchmodat2 syscall
Date: Thu, 10 Sep 2020 16:18:28 +0100 [thread overview]
Message-ID: <20200910151828.GD1236603@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200910142335.GG3265@brightrain.aerifal.cx>
On Thu, Sep 10, 2020 at 10:23:37AM -0400, Rich Felker wrote:
> It was determined (see glibc issue #14578 and commit a492b1e5ef) that,
> on some filesystems, performing chmod on the link itself produces a
> change in the inode's access mode, but returns an EOPNOTSUPP error.
Which filesystem types are those?
next prev parent reply other threads:[~2020-09-10 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 14:23 [PATCH] vfs: add fchmodat2 syscall Rich Felker
2020-09-10 15:18 ` Al Viro [this message]
2020-09-10 15:45 ` Rich Felker
2020-09-10 15:23 ` David Laight
2020-09-10 16:16 ` Greg KH
2020-09-10 16:35 ` Rich Felker
2020-09-10 16:20 ` Christoph Hellwig
2020-09-10 16:39 ` Rich Felker
2020-09-10 16:42 ` Christoph Hellwig
2020-09-10 17:02 ` Rich Felker
2020-09-11 6:57 ` Christoph Hellwig
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=20200910151828.GD1236603@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dalias@libc.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).