From: Christian Brauner <[email protected]>
To: Mateusz Guzik <[email protected]>
Cc: Christian Brauner <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected]
Subject: Re: [PATCH] fs: dodge an atomic in putname if ref == 1
Date: Wed, 12 Mar 2025 09:36:00 +0100 [thread overview]
Message-ID: <20250312-zwang-farbbeutel-a4c031fd05df@brauner> (raw)
In-Reply-To: <[email protected]>
On Tue, 11 Mar 2025 19:18:04 +0100, Mateusz Guzik wrote:
> While the structure is refcounted, the only consumer incrementing it is
> audit and even then the atomic operation is only needed when it
> interacts with io_uring.
>
> If putname spots a count of 1, there is no legitimate way for anyone to
> bump it.
>
> [...]
Applied to the vfs-6.15.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.15.misc 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.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.15.misc
[1/1] fs: dodge an atomic in putname if ref == 1
https://git.kernel.org/vfs/vfs/c/c93617c0f22c
next prev parent reply other threads:[~2025-03-12 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 18:18 [PATCH] fs: dodge an atomic in putname if ref == 1 Mateusz Guzik
2025-03-12 8:36 ` Christian Brauner [this message]
2025-03-12 15:51 ` Jan Kara
2025-03-12 16:07 ` Jens Axboe
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=20250312-zwang-farbbeutel-a4c031fd05df@brauner \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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