All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
	Andreas Dilger <adilger@sun.com>,
	akpm@osdl.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fix #11321: create /proc/ext4/*/stats et al more carefully
Date: Mon, 8 Sep 2008 10:39:51 -0400	[thread overview]
Message-ID: <20080908143951.GH8161@mit.edu> (raw)
In-Reply-To: <20080907164130.GA3376@x200.localdomain>

On Sun, Sep 07, 2008 at 08:41:30PM +0400, Alexey Dobriyan wrote:
> 
> register_disk() uses '!' too, BTW.
> 

Yeah, I guess it's good to be consistent with what's being broadcast
via udev et al.  I still that '!' in pathnames or '/' in device names
is really gross and shows no taste, though.  :-)

Here's what I've checked into the ext4 patch queue for submission to
mainline at the next merge window.  I've added a bit more error
checking in case proc_mkdir() fails and returns NULL.

						- Ted

ext4: fix #11321: create /proc/ext4/*/stats more carefully

From: Alexey Dobriyan <adobriyan@gmail.com>

ext4 creates per-suberblock directory in /proc/ext4/ . Name used as
basis is taken from bdevname, which, surprise, can contain slash.

However, proc while allowing to use proc_create("a/b", parent) form of
PDE creation, assumes that parent/a was already created.

bdevname in question is 'cciss/c0d0p9', directory is not created and all
this stuff goes directly into /proc (which is real bug).

Warning comes when _second_ partition is mounted.

http://bugzilla.kernel.org/show_bug.cgi?id=11321

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 2721643..984144d 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -2785,14 +2785,19 @@ static int ext4_mb_init_per_dev_proc(struct super_block *sb)
 	mode_t mode = S_IFREG | S_IRUGO | S_IWUSR;
 	struct ext4_sb_info *sbi = EXT4_SB(sb);
 	struct proc_dir_entry *proc;
-	char devname[64];
+	char devname[64], *p;
 
 	if (proc_root_ext4 == NULL) {
 		sbi->s_mb_proc = NULL;
 		return -EINVAL;
 	}
 	bdevname(sb->s_bdev, devname);
+	while (p = strchr(p, '/'))
+		*p = '!';
+
 	sbi->s_mb_proc = proc_mkdir(devname, proc_root_ext4);
+	if (!sbi->s_mb_proc)
+		goto err_create_dir;
 
 	MB_PROC_HANDLER(EXT4_MB_STATS_NAME, stats);
 	MB_PROC_HANDLER(EXT4_MB_MAX_TO_SCAN_NAME, max_to_scan);
@@ -2804,7 +2809,6 @@ static int ext4_mb_init_per_dev_proc(struct super_block *sb)
 	return 0;
 
 err_out:
-	printk(KERN_ERR "EXT4-fs: Unable to create %s\n", devname);
 	remove_proc_entry(EXT4_MB_GROUP_PREALLOC, sbi->s_mb_proc);
 	remove_proc_entry(EXT4_MB_STREAM_REQ, sbi->s_mb_proc);
 	remove_proc_entry(EXT4_MB_ORDER2_REQ, sbi->s_mb_proc);
@@ -2813,6 +2817,8 @@ err_out:
 	remove_proc_entry(EXT4_MB_STATS_NAME, sbi->s_mb_proc);
 	remove_proc_entry(devname, proc_root_ext4);
 	sbi->s_mb_proc = NULL;
+err_create_dir:
+	printk(KERN_ERR "EXT4-fs: Unable to create %s\n", devname);
 
 	return -ENOMEM;
 }

  reply	other threads:[~2008-09-08 14:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 21:06 [PATCH] ext4: fix #11321: create /proc/ext4/*/stats et al more carefully Alexey Dobriyan
2008-09-06  7:57 ` Andreas Dilger
2008-09-07 12:15   ` Alexey Dobriyan
2008-09-07 16:04     ` Ralf Hildebrandt
2008-09-07 16:24     ` Theodore Tso
2008-09-07 16:41       ` Alexey Dobriyan
2008-09-08 14:39         ` Theodore Tso [this message]
2008-09-09  7:06           ` Alexey Dobriyan
2008-09-09  7:12             ` Andrew Morton
2008-09-09 13:09               ` Theodore Tso
2008-09-09 18:10                 ` Andrew Morton
2008-09-09 18:24                   ` Theodore Tso
2008-09-09 18:29                     ` Andrew Morton
2008-09-09  7:19           ` Alexey Dobriyan
2008-09-09 11:51 ` Christoph Hellwig

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=20080908143951.GH8161@mit.edu \
    --to=tytso@mit.edu \
    --cc=Ralf.Hildebrandt@charite.de \
    --cc=adilger@sun.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-ext4@vger.kernel.org \
    /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.