From: Amir Goldstein <amir73il@gmail.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: miklos@szeredi.hu, fuse-devel@lists.linux.dev
Subject: Re: [PATCH v1 00/13] fuse: dir.c cleanups
Date: Fri, 24 Apr 2026 09:51:20 +0200 [thread overview]
Message-ID: <aesg-JcefprjeQfd@amir-ThinkPad-T480> (raw)
In-Reply-To: <20260424011646.457682-1-joannelkoong@gmail.com>
On Thu, Apr 23, 2026 at 06:16:33PM -0700, Joanne Koong wrote:
> Amir expressed his unhappiness [1] with some of the code structure in dir.c,
> particularly fuse_dentry_revalidate().
>
> This patchset is a series of cleanups in dir.c. There are no functional
> changes intended (except for the first patch).
I think this is not a good idea.
These sort of cleanup (e.g. removing unneeded gotos) are a kin to
whitespace cleanups - we should not do them unless going to change
the function for another reason.
The churn this creates and backporting conflicts are not worth the
win of the cleanup itself.
Therefore, please drop all but the fuse_dentry_revalidate() patch
which should be part of your passthrough series.
I will review only this one patch.
Thanks,
Amir.
>
> Thanks,
> Joanne
>
> [1] https://lore.kernel.org/fuse-devel/CAOQ4uxgCezMh3jdp519Lp9OZeqAyZHmc4Mp3FthJpfXhVoHEfw@mail.gmail.com/
>
> Joanne Koong (13):
> fuse: fix missing forget requests in error paths
> fuse: clean up fuse_lookup_name()
> fuse: clean up fuse_lookup()
> fuse: clean up fuse_dentry_revalidate()
> fuse: clean up fuse_create_open()
> fuse: clean up fuse_rename2()
> fuse: clean up fuse_time_to_jiffies()
> fuse: clean up fuse_link()
> fuse: clean up fuse_do_getattr()
> fuse: clean up fuse_update_get_attr()
> fuse: clean up fuse_get_link()
> fuse: clean up fuse_dir_open()
> fuse: clean up setattr()
>
> fs/fuse/dir.c | 324 ++++++++++++++++++++++++--------------------------
> 1 file changed, 154 insertions(+), 170 deletions(-)
>
> --
> 2.52.0
>
next prev parent reply other threads:[~2026-04-24 7:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 1:16 [PATCH v1 00/13] fuse: dir.c cleanups Joanne Koong
2026-04-24 1:16 ` [PATCH v1 01/13] fuse: fix missing forget requests in error paths Joanne Koong
2026-04-24 8:18 ` Amir Goldstein
2026-04-24 17:43 ` Joanne Koong
2026-04-24 1:16 ` [PATCH v1 02/13] fuse: clean up fuse_lookup_name() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 03/13] fuse: clean up fuse_lookup() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 04/13] fuse: clean up fuse_dentry_revalidate() Joanne Koong
2026-04-24 8:20 ` Amir Goldstein
2026-04-24 1:16 ` [PATCH v1 05/13] fuse: clean up fuse_create_open() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 06/13] fuse: clean up fuse_rename2() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 07/13] fuse: clean up fuse_time_to_jiffies() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 08/13] fuse: clean up fuse_link() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 09/13] fuse: clean up fuse_do_getattr() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 10/13] fuse: clean up fuse_update_get_attr() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 11/13] fuse: clean up fuse_get_link() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 12/13] fuse: clean up fuse_dir_open() Joanne Koong
2026-04-24 1:16 ` [PATCH v1 13/13] fuse: clean up setattr() Joanne Koong
2026-04-24 7:51 ` Amir Goldstein [this message]
2026-04-24 17:27 ` [PATCH v1 00/13] fuse: dir.c cleanups Joanne Koong
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=aesg-JcefprjeQfd@amir-ThinkPad-T480 \
--to=amir73il@gmail.com \
--cc=fuse-devel@lists.linux.dev \
--cc=joannelkoong@gmail.com \
--cc=miklos@szeredi.hu \
/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