From: Christian Brauner <brauner@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
trondmy@hammerspace.com, eggert@cs.ucla.edu, bruno@clisp.org,
Ondrej Valousek <ondrej.valousek.xm@renesas.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] fs: don't call posix_acl_listxattr in generic_listxattr
Date: Tue, 16 May 2023 16:17:37 +0200 [thread overview]
Message-ID: <20230516-notorisch-geblickt-6b591fbd77c1@brauner> (raw)
In-Reply-To: <20230516124655.82283-1-jlayton@kernel.org>
On Tue, 16 May 2023 08:46:54 -0400, Jeff Layton wrote:
> Commit f2620f166e2a caused the kernel to start emitting POSIX ACL xattrs
> for NFSv4 inodes, which it doesn't support. The only other user of
> generic_listxattr is HFS (classic) and it doesn't support POSIX ACLs
> either.
>
>
Applied to the vfs.misc.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.misc.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc.fixes
[1/1] fs: don't call posix_acl_listxattr in generic_listxattr
https://git.kernel.org/vfs/vfs/c/f3689fa785f0
next prev parent reply other threads:[~2023-05-16 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 12:46 [PATCH] fs: don't call posix_acl_listxattr in generic_listxattr Jeff Layton
2023-05-16 14:17 ` Christian Brauner [this message]
[not found] ` <TYXPR01MB18549D3A5B0BE777D7F6B284D9799@TYXPR01MB1854.jpnprd01.prod.outlook.com>
2023-05-16 21:22 ` A pass-through support for NFSv4 style ACL Jeff Layton
2023-05-17 7:42 ` Christian Brauner
2023-05-17 7:45 ` Christoph Hellwig
2023-05-17 7:50 ` Christian Brauner
2023-05-17 9:29 ` Ondrej Valousek
2023-05-17 9:58 ` Jeff Layton
2023-05-17 12:39 ` Theodore Ts'o
2023-05-19 10:56 ` Christian Brauner
2023-05-19 11:38 ` Ondrej Valousek
2023-05-19 12:02 ` Christian Brauner
2023-09-04 20:36 ` [PATCH] fs: don't call posix_acl_listxattr in generic_listxattr Ondrej Valousek
2023-09-05 10:50 ` Jeff Layton
2023-09-05 11:36 ` Ondrej Valousek
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=20230516-notorisch-geblickt-6b591fbd77c1@brauner \
--to=brauner@kernel.org \
--cc=bruno@clisp.org \
--cc=eggert@cs.ucla.edu \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ondrej.valousek.xm@renesas.com \
--cc=trondmy@hammerspace.com \
--cc=viro@zeniv.linux.org.uk \
/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).