All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] uninline may_mount() and don't opencode it in fspick(2)/fsopen(2)
Date: Fri, 20 May 2022 13:44:09 +0200	[thread overview]
Message-ID: <20220520114409.msh67ggnwu2hxpxa@wittgenstein> (raw)
In-Reply-To: <YocI5jIou18bDDuy@zeniv-ca.linux.org.uk>

On Fri, May 20, 2022 at 03:20:06AM +0000, Al Viro wrote:
> It's done once per (mount-related) syscall and there's no point
> whatsoever making it inline.
> 
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> ---

Looks good to me,
Reviewed-by: Christian Brauner (Microsoft) <brauner@kernel.org>

  parent reply	other threads:[~2022-05-20 11:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  3:17 [PATCHES] stuff from the last cycle that missed the window Al Viro
2022-05-20  3:17 ` [PATCH] fs/namei.c:reserve_stack(): tidy up the call of try_to_unlazy() Al Viro
2022-05-20 11:48   ` Christian Brauner
2022-05-20  3:18 ` [PATCH] get rid of dead code in legitimize_root() Al Viro
2022-05-20  3:20   ` [PATCH] uninline may_mount() and don't opencode it in fspick(2)/fsopen(2) Al Viro
2022-05-20  3:20     ` [PATCH] linux/mount.h: trim includes Al Viro
2022-05-20  3:22       ` [PATCH] m->mnt_root->d_inode->i_sb is a weird way to spell m->mnt_sb Al Viro
2022-05-20  3:23         ` [PATCH] blob_to_mnt(): kern_unmount() is needed to undo kern_mount() Al Viro
2022-05-20  3:23           ` [PATCH] move mount-related externs from fs.h to mount.h Al Viro
2022-05-20 11:54             ` Christian Brauner
2022-05-20 19:02           ` [PATCH] blob_to_mnt(): kern_unmount() is needed to undo kern_mount() Eric W. Biederman
2022-05-20 11:45       ` [PATCH] linux/mount.h: trim includes Christian Brauner
2022-05-20 11:44     ` Christian Brauner [this message]
2022-05-20 11:43   ` [PATCH] get rid of dead code in legitimize_root() 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=20220520114409.msh67ggnwu2hxpxa@wittgenstein \
    --to=brauner@kernel.org \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.