public inbox for linux-security-module@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neil@brown.name>,
	Christian Brauner <brauner@kernel.org>,
	 Alexander Viro <viro@zeniv.linux.org.uk>,
	David Howells <dhowells@redhat.com>, Jan Kara <jack@suse.cz>,
	Chuck Lever <chuck.lever@oracle.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Amir Goldstein	 <amir73il@gmail.com>,
	John Johansen <john.johansen@canonical.com>,
	Paul Moore	 <paul@paul-moore.com>,
	James Morris <jmorris@namei.org>,
	"Serge E. Hallyn"	 <serge@hallyn.com>,
	Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: linux-kernel@vger.kernel.org, netfs@lists.linux.dev,
	 linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
	 linux-unionfs@vger.kernel.org, apparmor@lists.ubuntu.com,
	 linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH 01/13] fs/proc: Don't lock root inode when creating "self" and "thread-self"
Date: Thu, 05 Feb 2026 07:33:26 -0500	[thread overview]
Message-ID: <b62d43c08545d26772a5fff45f13832767d766bb.camel@kernel.org> (raw)
In-Reply-To: <20260204050726.177283-2-neilb@ownmail.net>

On Wed, 2026-02-04 at 15:57 +1100, NeilBrown wrote:
> From: NeilBrown <neil@brown.name>
> 
> proc_setup_self() and proc_setup_thread_self() are only called from
> proc_fill_super() which is before the filesystem is "live".  So there is
> no need to lock the root directory when adding "self" and "thread-self".
> This is clear from simple_fill_super() which provides similar
> functionality for other filesystems and does not lock anything.
> 
> The locking is not harmful, except that it may be confusing to a reader.
> As part of a an effort to centralise all locking for directories for
> name-based operations (prior to changing some locking rules), it is
> simplest to remove the locking here.
> 
> Signed-off-by: NeilBrown <neil@brown.name>
> ---
>  fs/proc/self.c        | 3 ---
>  fs/proc/thread_self.c | 3 ---
>  2 files changed, 6 deletions(-)
> 
> diff --git a/fs/proc/self.c b/fs/proc/self.c
> index 62d2c0cfe35c..56adf1c68f7a 100644
> --- a/fs/proc/self.c
> +++ b/fs/proc/self.c
> @@ -35,11 +35,9 @@ unsigned self_inum __ro_after_init;
>  
>  int proc_setup_self(struct super_block *s)
>  {
> -	struct inode *root_inode = d_inode(s->s_root);
>  	struct dentry *self;
>  	int ret = -ENOMEM;
>  
> -	inode_lock(root_inode);
>  	self = d_alloc_name(s->s_root, "self");
>  	if (self) {
>  		struct inode *inode = new_inode(s);
> @@ -55,7 +53,6 @@ int proc_setup_self(struct super_block *s)
>  		}
>  		dput(self);
>  	}
> -	inode_unlock(root_inode);
>  
>  	if (ret)
>  		pr_err("proc_fill_super: can't allocate /proc/self\n");
> diff --git a/fs/proc/thread_self.c b/fs/proc/thread_self.c
> index d6113dbe58e0..61ac62c3fd9f 100644
> --- a/fs/proc/thread_self.c
> +++ b/fs/proc/thread_self.c
> @@ -35,11 +35,9 @@ unsigned thread_self_inum __ro_after_init;
>  
>  int proc_setup_thread_self(struct super_block *s)
>  {
> -	struct inode *root_inode = d_inode(s->s_root);
>  	struct dentry *thread_self;
>  	int ret = -ENOMEM;
>  
> -	inode_lock(root_inode);
>  	thread_self = d_alloc_name(s->s_root, "thread-self");
>  	if (thread_self) {
>  		struct inode *inode = new_inode(s);
> @@ -55,7 +53,6 @@ int proc_setup_thread_self(struct super_block *s)
>  		}
>  		dput(thread_self);
>  	}
> -	inode_unlock(root_inode);
>  
>  	if (ret)
>  		pr_err("proc_fill_super: can't allocate /proc/thread-self\n");

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-02-05 12:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04  4:57 [PATCH 00/13] Further centralising of directory locking for name ops NeilBrown
2026-02-04  4:57 ` [PATCH 01/13] fs/proc: Don't lock root inode when creating "self" and "thread-self" NeilBrown
2026-02-05 12:33   ` Jeff Layton [this message]
2026-02-04  4:57 ` [PATCH 02/13] VFS: move the start_dirop() kerndoc comment to before start_dirop() NeilBrown
2026-02-05 12:33   ` Jeff Layton
2026-02-04  4:57 ` [PATCH 03/13] libfs: change simple_done_creating() to use end_creating() NeilBrown
2026-02-05 12:19   ` Jeff Layton
2026-02-06  2:13     ` NeilBrown
2026-02-04  4:57 ` [PATCH 04/13] Apparmor: Use simple_start_creating() / simple_done_creating() NeilBrown
2026-02-04 10:58   ` kernel test robot
2026-02-05 12:58   ` Jeff Layton
2026-02-06  0:21     ` NeilBrown
2026-02-04  4:57 ` [PATCH 05/13] selinux: " NeilBrown
2026-02-05 12:36   ` Jeff Layton
2026-02-20 22:47   ` Paul Moore
2026-02-21 22:28     ` NeilBrown
2026-02-22 14:19       ` Paul Moore
2026-02-23  0:58         ` NeilBrown
2026-02-04  4:57 ` [PATCH 06/13] nfsd: switch purge_old() to use start_removing_noperm() NeilBrown
2026-02-05 12:36   ` Jeff Layton
2026-02-04  4:57 ` [PATCH 07/13] VFS: make lookup_one_qstr_excl() static NeilBrown
2026-02-05 12:37   ` Jeff Layton
2026-02-04  4:57 ` [PATCH 08/13] ovl: Simplify ovl_lookup_real_one() NeilBrown
2026-02-05 12:38   ` Jeff Layton
2026-02-05 13:04     ` Amir Goldstein
2026-02-06  0:43       ` NeilBrown
2026-02-04  4:57 ` [PATCH 09/13] cachefiles: change cachefiles_bury_object to use start_renaming_dentry() NeilBrown
2026-02-05 12:38   ` Jeff Layton
2026-02-04  4:57 ` [PATCH 10/13] ovl: change ovl_create_real() to get a new lock when re-opening created file NeilBrown
2026-02-05 12:26   ` Amir Goldstein
2026-02-06  1:11     ` NeilBrown
2026-02-06 13:35       ` Amir Goldstein
2026-02-04  4:57 ` [PATCH 11/13] ovl: use is_subdir() for testing if one thing is a subdir of another NeilBrown
2026-02-05  9:37   ` Amir Goldstein
2026-02-05 12:38   ` Jeff Layton
2026-02-04  4:57 ` [PATCH 12/13] ovl: remove ovl_lock_rename_workdir() NeilBrown
2026-02-05  9:45   ` Amir Goldstein
2026-02-06  1:18     ` NeilBrown
2026-02-05 12:40   ` Jeff Layton
2026-02-05 12:58   ` Jeff Layton
2026-02-04  4:57 ` [PATCH 13/13] VFS: unexport lock_rename(), lock_rename_child(), unlock_rename() NeilBrown
2026-02-05 12:41   ` Jeff Layton

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=b62d43c08545d26772a5fff45f13832767d766bb.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=apparmor@lists.ubuntu.com \
    --cc=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dhowells@redhat.com \
    --cc=jack@suse.cz \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neil@brown.name \
    --cc=netfs@lists.linux.dev \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=stephen.smalley.work@gmail.com \
    --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