mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, xiaosuo@gmail.com
Subject: Re: + procfs-directory-entry-cleanup.patch added to -mm tree
Date: Tue, 22 May 2007 11:29:51 -0700	[thread overview]
Message-ID: <20070522112951.1a980a46.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070522174348.GA5689@martell.zuzino.mipt.ru>

On Tue, 22 May 2007 21:43:49 +0400
Alexey Dobriyan <adobriyan@gmail.com> wrote:

> On Sun, May 20, 2007 at 08:41:02PM -0700, akpm@linux-foundation.org wrote:
> > Subject: procfs directory entry cleanup
> > From: "Changli Gao" <xiaosuo@gmail.com>
> >
> > Function proc_register() will assign proc_dir_operations and
> > proc_dir_inode_operations to ent's members proc_fops and proc_iops
> > correctly if ent is a directory. So the early assignment isn't
> > necessary.
> 
> > --- a/fs/proc/generic.c~procfs-directory-entry-cleanup
> > +++ a/fs/proc/generic.c
> > @@ -649,9 +649,6 @@ struct proc_dir_entry *proc_mkdir_mode(c
> >  
> >  	ent = proc_create(&parent, name, S_IFDIR | mode, 2);
> >  	if (ent) {
> > -		ent->proc_fops = &proc_dir_operations;
> > -		ent->proc_iops = &proc_dir_inode_operations;
> > -
> >  		if (proc_register(parent, ent) < 0) {
> >  			kfree(ent);
> >  			ent = NULL;
> > @@ -686,10 +683,6 @@ struct proc_dir_entry *create_proc_entry
> >  
> >  	ent = proc_create(&parent,name,mode,nlink);
> >  	if (ent) {
> > -		if (S_ISDIR(mode)) {
> > -			ent->proc_fops = &proc_dir_operations;
> > -			ent->proc_iops = &proc_dir_inode_operations;
> > -		}
> >  		if (proc_register(parent, ent) < 0) {
> >  			kfree(ent);
> >  			ent = NULL;
> 
> This should add race because new PDE for directory will be glued to tree
> with NULL ->proc_iops and, at least, vfs_getattr() doesn't check for
> NULL ->i_op.
> 
> I've tried to reproduce this scenario with udelay() inserted before
> S_ISDIR checks in proc_register() but got some panic while in X,
> so no cookie for me. Maybe it's impossible, indeed.
> 
> Anyway, this patch + moving ->proc_fops and ->proc_iops initialization
> before gluing is OK with me.

Like this?

diff -puN fs/proc/generic.c~procfs-directory-entry-cleanup-fix fs/proc/generic.c
--- a/fs/proc/generic.c~procfs-directory-entry-cleanup-fix
+++ a/fs/proc/generic.c
@@ -529,12 +529,6 @@ static int proc_register(struct proc_dir
 		return -EAGAIN;
 	dp->low_ino = i;
 
-	spin_lock(&proc_subdir_lock);
-	dp->next = dir->subdir;
-	dp->parent = dir;
-	dir->subdir = dp;
-	spin_unlock(&proc_subdir_lock);
-
 	if (S_ISDIR(dp->mode)) {
 		if (dp->proc_iops == NULL) {
 			dp->proc_fops = &proc_dir_operations;
@@ -550,6 +544,13 @@ static int proc_register(struct proc_dir
 		if (dp->proc_iops == NULL)
 			dp->proc_iops = &proc_file_inode_operations;
 	}
+
+	spin_lock(&proc_subdir_lock);
+	dp->next = dir->subdir;
+	dp->parent = dir;
+	dir->subdir = dp;
+	spin_unlock(&proc_subdir_lock);
+
 	return 0;
 }
 
_


  reply	other threads:[~2007-05-22 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705210341.l4L3f1BH001692@shell0.pdx.osdl.net>
2007-05-22 17:43 ` Alexey Dobriyan
2007-05-22 18:29   ` Andrew Morton [this message]
2007-05-22 20:16     ` Alexey Dobriyan

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=20070522112951.1a980a46.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiaosuo@gmail.com \
    /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®