From: Christian Brauner <christian@brauner.io>
To: viro@zeniv.linux.org.uk, dhowells@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] fsopen: use square brackets around "fscontext"
Date: Thu, 9 May 2019 17:39:04 +0200 [thread overview]
Message-ID: <20190509153902.tqkoooxtviafrla5@brauner.io> (raw)
In-Reply-To: <20190508152509.13336-2-christian@brauner.io>
On Wed, May 08, 2019 at 05:25:09PM +0200, Christian Brauner wrote:
> Make the name of the anon inode fd "[fscontext]" instead of "fscontext".
> This is minor but most core-kernel anon inode fds carry square brackets
> around their name (cf. [1]). For the sake of consistency lets do the same
This "(cf. [1])" reference was supposed to point to the list below. But
since I rewrote the paragraph it can simply be dropped. Sorry for the
oversight.
Christian
> for the mount api:
>
> [eventfd]
> [eventpoll]
> [fanotify]
> [fscontext]
> [io_uring]
> [pidfd]
> [signalfd]
> [timerfd]
> [userfaultfd]
>
> Signed-off-by: Christian Brauner <christian@brauner.io>
> ---
> 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);
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-05-09 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 15:25 [PATCH v1 1/2] fs: make all new mount api fds cloexec by default Christian Brauner
2019-05-08 15:25 ` [PATCH v1 2/2] fsopen: use square brackets around "fscontext" Christian Brauner
2019-05-09 15:39 ` Christian Brauner [this message]
2019-05-09 15:39 ` Christian Brauner
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=20190509153902.tqkoooxtviafrla5@brauner.io \
--to=christian@brauner.io \
--cc=dhowells@redhat.com \
--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
all inboxes | Powered by JetHome®