From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Jan Kara <jack@suse.cz>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: VFS minor improvements policy
Date: Wed, 18 Mar 2026 21:51:43 +0100 (CET) [thread overview]
Message-ID: <2095030362.2263405.1773867103100@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <pjfdjimwb3br5wtut4a5q4xdys2mgf2d3hkajvinyphhoziaum@u55pnnlrfmgz>
> Op 17-03-2026 09:31 CET schreef Jan Kara <jack@suse.cz>:
>
> I guess this is a bit matter of personal preference. I personally would
> prefer explicitely named enum in this case and use it where appropriate but
> Al? apparently preferred brewity and used 'int' everywhere. The borderline
> between "useless typedefs" and "documentation by types" is blurry. I'd say
> trying to "fix" this would do more harm than good.
>
I understand. I've been traveling a bit through namei.c and open.c, and I come
across quite some things I think may not be quite right. However, I also understand
that I am an idiot, and so it is hard sometimes to judge what to send in :)
For instance, I am quite positive that there is some dead code in the fd allocation
slow path. And I've been puzzled the last two days about nd->depth, and if it can
even ever be > 1. I try sometimes to spar with Claude, but you can just never rely on
it. Just bear with me, and I apologize in advance if I ever send in something silly.
I am just trying to learn.
>
> If the documentation / comment is pointless or even wrong, that's
> definitely worth a fix. They are just not treated with particularly high
> priority but they are definitely needed.
>
Noted.
Thanks,
Jori.
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
prev parent reply other threads:[~2026-03-18 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 13:24 VFS minor improvements policy Jori Koolstra
2026-03-17 8:31 ` Jan Kara
2026-03-17 14:17 ` Christian Brauner
2026-03-18 20:55 ` Jori Koolstra
2026-03-18 20:51 ` Jori Koolstra [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=2095030362.2263405.1773867103100@kpc.webmail.kpnmail.nl \
--to=jkoolstra@xs4all.nl \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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