From: David Laight <David.Laight@ACULAB.COM>
To: 'Ameer Hamza' <ahamza@ixsystems.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"guoren@kernel.org" <guoren@kernel.org>,
"palmer@rivosinc.com" <palmer@rivosinc.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"slark_xiao@163.com" <slark_xiao@163.com>,
"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
"ink@jurassic.park.msu.ru" <ink@jurassic.park.msu.ru>,
"mattst88@gmail.com" <mattst88@gmail.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"deller@gmx.de" <deller@gmx.de>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"awalker@ixsystems.com" <awalker@ixsystems.com>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>
Subject: RE: [PATCH v2] Add new open(2) flag - O_EMPTY_PATH
Date: Mon, 2 Jan 2023 14:01:38 +0000 [thread overview]
Message-ID: <4b39cf528148470c934fb5823b35e9d5@AcuMS.aculab.com> (raw)
In-Reply-To: <20221231235618.117201-1-ahamza@ixsystems.com>
From: Ameer Hamza
> Sent: 31 December 2022 23:56
>
> This patch adds a new flag O_EMPTY_PATH that allows openat and open
> system calls to open a file referenced by fd if the path is empty,
> and it is very similar to the FreeBSD O_EMPTY_PATH flag. This can be
> beneficial in some cases since it would avoid having to grant /proc
> access to things like samba containers for reopening files to change
> flags in a race-free way.
>
But what does it do?
(Apart from add code to a common kernel code path.)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2023-01-02 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 16:02 [PATCH] Add new open(2) flag - O_EMPTY_PATH Ameer Hamza
2022-12-31 0:15 ` kernel test robot
2022-12-31 23:56 ` [PATCH v2] " Ameer Hamza
2023-01-01 11:16 ` kernel test robot
2023-01-01 15:37 ` [PATCH v3] " Ameer Hamza
2023-01-02 14:01 ` David Laight [this message]
2023-01-02 14:35 ` [PATCH v2] " Ameer Hamza
2023-01-06 9:21 ` David Laight
2023-01-06 13:06 ` [PATCH] " Christian Brauner
2023-04-19 1:15 ` Ameer Hamza
[not found] ` <7454A798-1277-411A-853C-635B33439029@gmail.com>
2023-04-19 9:18 ` Christian Brauner
2023-04-19 21:29 ` David Laight
2023-04-26 13:10 ` Andrew Walker
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=4b39cf528148470c934fb5823b35e9d5@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ahamza@ixsystems.com \
--cc=arnd@arndb.de \
--cc=awalker@ixsystems.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=f.fainelli@gmail.com \
--cc=guoren@kernel.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jlayton@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=palmer@rivosinc.com \
--cc=richard.henderson@linaro.org \
--cc=slark_xiao@163.com \
--cc=sparclinux@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;
as well as URLs for NNTP newsgroup(s).