[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30a5fe67500c40a4d5f9516e9b549ec796faac74.camel@xry111.site>
Date: Tue, 25 Jun 2024 18:51:19 +0800
From: Xi Ruoyao <xry111@...111.site>
To: Christian Brauner <brauner@...nel.org>, Mateusz Guzik <mjguzik@...il.com>
Cc: Alexander Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>, Linus
Torvalds <torvalds@...ux-foundation.org>, Alejandro Colomar
<alx@...nel.org>, Arnd Bergmann <arnd@...db.de>, Huacai Chen
<chenhuacai@...ngson.cn>, Xuerui Wang <kernel@...0n.name>, Jiaxun Yang
<jiaxun.yang@...goat.com>, Icenowy Zheng <uwu@...nowy.me>,
linux-fsdevel@...r.kernel.org, linux-arch@...r.kernel.org,
loongarch@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] vfs: Shortcut AT_EMPTY_PATH early for statx, and add
AT_NO_PATH for statx and fstatat
On Tue, 2024-06-25 at 10:50 +0200, Christian Brauner wrote:
> No, let's not waste AT_* flag space in fear of some hypothetical
> breakage. Let's try it cleanly first and make AT_EMPTY_PATH work with
> NULL paths.
>
> Note, I started working on this (checks ...) 30th April but then some
> other work came up and I never got back to it (Sorry, Linus). I pushed
> the branch to #vfs.empty.path now. The top three commits was what I had
> started doing.
>
> It was based on a new vfs_empty_path() helper so we could reuse it for
> other system calls as well.
If I understand correctly, I should submit a patch against
vfs.empty.path making statx(fd, NULL, AT_EMPTY_PATH) work then?
--
Xi Ruoyao <xry111@...111.site>
School of Aerospace Science and Technology, Xidian University
Powered by blists - more mailing lists