From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org, viro@zeniv.linux.org.uk
Cc: Christian Brauner <christian@brauner.io>,
dhowells@redhat.com, christian@brauner.io, arnd@arndb.de,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/4] uapi, fsopen: use square brackets around "fscontext"
Date: Thu, 16 May 2019 12:23:51 +0100 [thread overview]
Message-ID: <155800583139.26930.1622199753566005728.stgit@warthog.procyon.org.uk> (raw)
In-Reply-To: <155800581545.26930.2167325198332902897.stgit@warthog.procyon.org.uk>
From: Christian Brauner <christian@brauner.io>
Make the name of the anon inode fd "[fscontext]" instead of "fscontext".
This is minor but most core-kernel anon inode fds already carry square
brackets around their name:
[eventfd]
[eventpoll]
[fanotify]
[io_uring]
[pidfd]
[signalfd]
[timerfd]
[userfaultfd]
For the sake of consistency lets do the same for the fscontext anon inode
fd that comes with the new mount api.
Signed-off-by: Christian Brauner <christian@brauner.io>
Signed-off-by: David Howells <dhowells@redhat.com>
---
fs/fsopen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fsopen.c b/fs/fsopen.c
index a38fa8c616cf..83d0d2001bb2 100644
--- a/fs/fsopen.c
+++ b/fs/fsopen.c
@@ -92,7 +92,7 @@ static int fscontext_create_fd(struct fs_context *fc)
{
int fd;
- fd = anon_inode_getfd("fscontext", &fscontext_fops, fc,
+ fd = anon_inode_getfd("[fscontext]", &fscontext_fops, fc,
O_RDWR | O_CLOEXEC);
if (fd < 0)
put_fs_context(fc);
next prev parent reply other threads:[~2019-05-16 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 11:23 [PATCH 0/4] uapi, vfs: Change the mount API UAPI David Howells
2019-05-16 11:23 ` [PATCH 1/4] uapi, fs: make all new mount api fds cloexec by default David Howells
2019-05-16 11:23 ` David Howells [this message]
2019-05-16 11:23 ` [PATCH 3/4] uapi, x86: Fix the syscall numbering of the mount API syscalls David Howells
2019-05-16 11:29 ` Arnd Bergmann
2019-05-16 11:24 ` [PATCH 4/4] uapi: Wire up the mount API syscalls on non-x86 arches David Howells
2019-05-16 11:32 ` Arnd Bergmann
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=155800583139.26930.1622199753566005728.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=arnd@arndb.de \
--cc=christian@brauner.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).