From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Alexander Aring <alex.aring@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Mike Rapoport <rppt@kernel.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <ljs@kernel.org>,
zhang jiao <zhangjiao2@cmss.chinamobile.com>,
Kees Cook <kees@kernel.org>,
Penglei Jiang <superman.xpt@gmail.com>,
Ethan Tidmore <ethantidmore06@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
wangzijie <wangzijie1@honor.com>, NeilBrown <neil@brown.name>,
Amir Goldstein <amir73il@gmail.com>,
Mateusz Guzik <mjguzik@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: [PATCH] vfs: transitive upgrade restrictions for fds
Date: Thu, 26 Mar 2026 12:09:08 +0100 (CET) [thread overview]
Message-ID: <95547355.15637.1774523348666@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <2026032403-slapstick-anvil-a68e@gregkh>
> Op 24-03-2026 15:37 CET schreef Greg KH <gregkh@linuxfoundation.org>:
>
> Any chance to get a test for this as well to know if this keeps working
> (or works at all)?
>
I do have some tests, can shape them up a bit so that they may go in selftest
(if this fd stuff goes through). How should I do this? Send all as a v2, or
inline it as a response here?
> > /*
> > * Helper to directly jump to a known parsed path from ->get_link,
> > * caller must have taken a reference to path beforehand.
> > */
> > -int nd_jump_link(const struct path *path)
> > +int nd_jump_link_how(const struct path *path, const struct jump_how how)
>
> Shouldn't that be "const struct jump_how *how"?
>
> Or do you really want to pass this structure on the stack?
>
I save a pointer indirection, and jump_how is right now just an int. That was
at least my reasoning here.
> thanks,
>
> greg k-h
Thanks,
Jori.
next prev parent reply other threads:[~2026-03-26 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 22:00 [RFC PATCH 0/1] vfs: transitive upgrade restrictions for fds Jori Koolstra
2026-03-23 22:00 ` [PATCH] " Jori Koolstra
2026-03-24 8:41 ` Christian Brauner
2026-03-24 14:37 ` Greg KH
2026-03-26 11:09 ` Jori Koolstra [this message]
2026-03-24 12:31 ` [RFC PATCH 0/1] " Jeff Layton
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=95547355.15637.1774523348666@kpc.webmail.kpnmail.nl \
--to=jkoolstra@xs4all.nl \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alex.aring@gmail.com \
--cc=amir73il@gmail.com \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=david@redhat.com \
--cc=ethantidmore06@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=kees@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mjguzik@gmail.com \
--cc=neil@brown.name \
--cc=oleg@redhat.com \
--cc=rppt@kernel.org \
--cc=superman.xpt@gmail.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wangzijie1@honor.com \
--cc=zhangjiao2@cmss.chinamobile.com \
/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