From: Chris Mason <clm@meta.com>
To: Mateusz Guzik <mjguzik@gmail.com>,
brauner@kernel.org, viro@zeniv.linux.org.uk
Cc: jack@suse.cz, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH v2] fs: touch up symlink clean up in lookup
Date: Thu, 18 Dec 2025 12:11:24 -0500 [thread overview]
Message-ID: <92a32c99-d996-480f-8641-d8dca1a077c1@meta.com> (raw)
In-Reply-To: <20251217112345.2340007-1-mjguzik@gmail.com>
On 12/17/25 6:23 AM, Mateusz Guzik wrote:
> Provide links_cleanup_rcu() and links_cleanup_ref() for rcu- and ref-
> walks respectively.
>
> The somewhat misleading drop_links() gets renamed to links_issue_delayed_calls(),
> which spells out what it is actually doing.
>
> There are no changes in behavior, this however should be less
> error-prone going forward.
>
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
> ---
> fs/namei.c | 45 ++++++++++++++++++++++++++++++++-------------
> 1 file changed, 32 insertions(+), 13 deletions(-)
>
> v2:
> - remove the mindless copy-paste in links_cleanup_ref, instead only move
> path_puts on the symlinks
>
> this performs path_put on nd->path later, which should not be a material
> difference.
>
> this assumes the LOOKUP_CACHED fixup is applied:
> https://lore.kernel.org/linux-fsdevel/20251217104854.GU1712166@ZenIV/T/#mff14d1dd88729f40fa94ada8beaa64e0c41097ff
>
> technically the 2 patches could be combined, but I did not want to do it
> given the bug
>
> Chris, can you feed this thing into the magic llm? Better yet, is it
> something I can use myself? I passed the known buggy patch to gcc
> -fanalyze and clang --analyze and neither managed to point out any
> issues.
>
Looks like you and Al are still discussing the specifics, but I ran this
version through the review prompts and it didn't find any problems.
With claude or gemini subscriptions, you can run them locally:
https://github.com/masoncl/review-prompts
(Other AI providers may work too, but those are the only two I've heard
about so far)
-chris
prev parent reply other threads:[~2025-12-18 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:23 Mateusz Guzik
2025-12-17 11:38 ` Al Viro
2025-12-17 11:45 ` Mateusz Guzik
2025-12-18 17:11 ` Chris Mason [this message]
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=92a32c99-d996-480f-8641-d8dca1a077c1@meta.com \
--to=clm@meta.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@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®