From: Collin Funk <collin.funk1@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <stephen.smalley.work@gmail.com>,
linux-fsdevel@vger.kernel.org, brauner@kernel.org,
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: Thu, 05 Jun 2025 22:39:08 -0700 [thread overview]
Message-ID: <87plfhsa2r.fsf@gmail.com> (raw)
In-Reply-To: <CAHC9VhRUqpubkuFFVCfiMN4jDiEhXQvJ91vHjrM5d9e4bEopaw@mail.gmail.com>
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.
Collin
next prev parent reply other threads:[~2025-06-06 5:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 16:48 [PATCH] fs/xattr.c: fix simple_xattr_list() Stephen Smalley
2025-06-05 21:40 ` Paul Moore
2025-06-05 21:51 ` Paul Moore
2025-06-06 5:39 ` Collin Funk [this message]
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
2025-06-17 0:27 ` Collin Funk
-- strict thread matches above, loose matches on Subject: below --
2025-06-05 16:51 Stephen Smalley
2025-06-05 17:09 ` 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=87plfhsa2r.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=brauner@kernel.org \
--cc=bug-gnulib@gnu.org \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.