mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-fsdevel@vger.kernel.org,
	 Alexander Viro <viro@zeniv.linux.org.uk>,
	Collin Funk <collin.funk1@gmail.com>,
	 Stephen Smalley <stephen.smalley.work@gmail.com>,
	linux-kernel@vger.kernel.org, selinux@vger.kernel.org,
	 eggert@cs.ucla.edu, bug-gnulib@gnu.org
Subject: Re: [PATCH] fs/xattr.c: fix simple_xattr_list()
Date: Mon, 16 Jun 2025 16:13:09 +0200	[thread overview]
Message-ID: <20250616-flitzen-barmherzigen-e30c63f9e8ba@brauner> (raw)
In-Reply-To: <CAHC9VhTWEWq_rzZnjbYrS6MCb5_gSBDAjUoYQY4htQ5MaY2o_w@mail.gmail.com>

On Mon, Jun 16, 2025 at 10:03:52AM -0400, Paul Moore wrote:
> On Wed, Jun 11, 2025 at 6:05 AM Christian Brauner <brauner@kernel.org> wrote:
> > On Tue, Jun 10, 2025 at 07:50:10PM -0400, Paul Moore wrote:
> > > On Fri, Jun 6, 2025 at 1:39 AM Collin Funk <collin.funk1@gmail.com> wrote:
> > > > Paul Moore <paul@paul-moore.com> writes:
> > > > >> <stephen.smalley.work@gmail.com> wrote:
> > > > >> >
> > > > >> > commit 8b0ba61df5a1 ("fs/xattr.c: fix simple_xattr_list to always
> > > > >> > include security.* xattrs") failed to reset err after the call to
> > > > >> > security_inode_listsecurity(), which returns the length of the
> > > > >> > returned xattr name. This results in simple_xattr_list() incorrectly
> > > > >> > returning this length even if a POSIX acl is also set on the inode.
> > > > >> >
> > > > >> > Reported-by: Collin Funk <collin.funk1@gmail.com>
> > > > >> > Closes: https://lore.kernel.org/selinux/8734ceal7q.fsf@gmail.com/
> > > > >> > Reported-by: Paul Eggert <eggert@cs.ucla.edu>
> > > > >> > Closes: https://bugzilla.redhat.com/show_bug.cgi?id=2369561
> > > > >> > Fixes: 8b0ba61df5a1 ("fs/xattr.c: fix simple_xattr_list to always include security.* xattrs")
> > > > >> >
> > > > >> > Signed-off-by: Stephen Smalley <stephen.smalley.work@gmail.com>
> > > > >> > ---
> > > > >> >  fs/xattr.c | 1 +
> > > > >> >  1 file changed, 1 insertion(+)
> > > > >>
> > > > >> Reviewed-by: Paul Moore <paul@paul-moore.com>
> > > > >
> > > > > Resending this as it appears that Stephen's original posting had a
> > > > > typo in the VFS mailing list.  The original post can be found in the
> > > > > SELinux archives:
> > > > >
> > > > > https://lore.kernel.org/selinux/20250605164852.2016-1-stephen.smalley.work@gmail.com/
> > > >
> > > > Hi, responding to this message since it has the correct lists.
> > > >
> > > > I just booted into a kernel with this patch applied and confirm that it
> > > > fixes the Gnulib tests that were failing.
> > > >
> > > > Reviewed-by: Collin Funk <collin.funk1@gmail.com>
> > > > Tested-by: Collin Funk <collin.funk1@gmail.com>
> > > >
> > > > Thanks for the fix.
> > >
> > > Al, Christian, are either of you going to pick up this fix to send to
> > > Linus?  If not, any objection if I send this up?
> >
> > It's been in vfs.fixes for some time already and it'll go out with the
> > first round of post -rc1 fixes this week.
> 
> Checking on the status of this patch as we are at -rc2 and I don't see
> it in Linus' tree?

Sent this morning with some other fixes.

  reply	other threads:[~2025-06-16 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 16:48 Stephen Smalley
2025-06-05 21:40 ` Paul Moore
2025-06-05 21:51   ` Paul Moore
2025-06-06  5:39     ` Collin Funk
2025-06-10 23:50       ` Paul Moore
2025-06-11 10:05         ` Christian Brauner
2025-06-11 15:45           ` Paul Moore
2025-06-12 12:21             ` Christian Brauner
2025-06-12 12:54               ` Stephen Smalley
2025-06-16 14:03           ` Paul Moore
2025-06-16 14:13             ` Christian Brauner [this message]
2025-06-17  0:27               ` Collin Funk

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=20250616-flitzen-barmherzigen-e30c63f9e8ba@brauner \
    --to=brauner@kernel.org \
    --cc=bug-gnulib@gnu.org \
    --cc=collin.funk1@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.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

all inboxes | Powered by JetHome®