From: Paul Moore <paul@paul-moore.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, torvalds@linux-foundation.org,
brauner@kernel.org, jack@suse.cz, mjguzik@gmail.com,
axboe@kernel.dk, audit@vger.kernel.org,
io-uring@vger.kernel.org
Subject: Re: [RFC][PATCH 10/13] get rid of audit_reusename()
Date: Mon, 10 Nov 2025 19:23:10 -0500 [thread overview]
Message-ID: <CAHC9VhROakxXe-ZJNFtpNLeV+P8g5W4VZOdQtuY9NbaOHwEYuQ@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhQjzt0nJnbwXuwT7UPBwtHjEOPZu6z=c=G=+-Wdkuj5Vw@mail.gmail.com>
On Mon, Nov 10, 2025 at 6:13 PM Paul Moore <paul@paul-moore.com> wrote:
> On Sun, Nov 9, 2025 at 1:37 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > Originally we tried to avoid multiple insertions into audit names array
> > during retry loop by a cute hack - memorize the userland pointer and
> > if there already is a match, just grab an extra reference to it.
> >
> > Cute as it had been, it had problems - two identical pointers had
> > audit aux entries merged, two identical strings did not. Having
> > different behaviour for syscalls that differ only by addresses of
> > otherwise identical string arguments is obviously wrong - if nothing
> > else, compiler can decide to merge identical string literals.
> >
> > Besides, this hack does nothing for non-audited processes - they get
> > a fresh copy for retry. It's not time-critical, but having behaviour
> > subtly differ that way is bogus.
> >
> > These days we have very few places that import filename more than once
> > (9 functions total) and it's easy to massage them so we get rid of all
> > re-imports. With that done, we don't need audit_reusename() anymore.
> > There's no need to memorize userland pointer either.
> >
> > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> > ---
> > fs/namei.c | 11 +++--------
> > include/linux/audit.h | 11 -----------
> > include/linux/fs.h | 1 -
> > kernel/auditsc.c | 23 -----------------------
> > 4 files changed, 3 insertions(+), 43 deletions(-)
>
> Looks reasonable to me. Not sure if you've run it through the
> audit-testsuite yet, but I'm building a test kernel as I write this,
> I'll let you know how it goes.
>
> Acked-by: Paul Moore <paul@paul-moore.com>
FWIW, it passes the audit-testsuite.
Tested-by: Paul Moore <paul@paul-moore.com>
--
paul-moore.com
next prev parent reply other threads:[~2025-11-11 0:23 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 6:37 [RFC][PATCH 00/13] io_uring, struct filename and audit Al Viro
2025-11-09 6:37 ` [RFC][PATCH 01/13] do_faccessat(): import pathname only once Al Viro
2025-11-13 10:11 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 02/13] do_fchmodat(): " Al Viro
2025-11-13 10:12 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 03/13] do_fchownat(): " Al Viro
2025-11-13 10:13 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 04/13] do_utimes_path(): " Al Viro
2025-11-13 10:15 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 05/13] chdir(2): " Al Viro
2025-11-13 10:16 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 06/13] chroot(2): " Al Viro
2025-11-13 10:18 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 07/13] user_statfs(): " Al Viro
2025-11-13 10:18 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 08/13] do_sys_truncate(): " Al Viro
2025-11-13 10:18 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 09/13] do_readlinkat(): " Al Viro
2025-11-13 10:20 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 10/13] get rid of audit_reusename() Al Viro
2025-11-09 19:18 ` Linus Torvalds
2025-11-09 19:55 ` Mateusz Guzik
2025-11-09 20:22 ` Linus Torvalds
2025-11-09 22:18 ` Mateusz Guzik
2025-11-09 22:29 ` Linus Torvalds
2025-11-09 22:33 ` Mateusz Guzik
2025-11-09 22:39 ` Mateusz Guzik
2025-11-09 22:41 ` Linus Torvalds
2025-11-09 22:44 ` Linus Torvalds
2025-11-09 23:07 ` Linus Torvalds
2025-11-09 22:18 ` Linus Torvalds
2025-11-10 5:17 ` Al Viro
2025-11-10 16:41 ` Linus Torvalds
2025-11-10 19:58 ` Al Viro
2025-11-10 20:52 ` Linus Torvalds
2025-11-11 1:16 ` Al Viro
2025-11-12 9:26 ` Christian Brauner
2025-11-10 6:05 ` Al Viro
2025-11-10 6:36 ` Al Viro
2025-11-10 16:50 ` Linus Torvalds
2025-11-10 23:13 ` Paul Moore
2025-11-11 0:23 ` Paul Moore [this message]
2025-11-13 10:29 ` Jan Kara
2025-11-09 6:37 ` [RFC][PATCH 11/13] allow incomplete imports of filenames Al Viro
2025-11-11 0:45 ` Paul Moore
2025-11-11 14:41 ` Jens Axboe
2025-11-19 1:12 ` Al Viro
2025-11-19 1:14 ` Al Viro
2025-11-19 5:41 ` Al Viro
2025-11-09 6:37 ` [RFC][PATCH 12/13] fs: touch up predicts in putname() Al Viro
2025-11-09 6:37 ` [RFC][PATCH 13/13] struct filename ->refcnt doesn't need to be atomic Al Viro
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=CAHC9VhROakxXe-ZJNFtpNLeV+P8g5W4VZOdQtuY9NbaOHwEYuQ@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=audit@vger.kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=torvalds@linux-foundation.org \
--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