From: Jeff Mahoney <jeffm@suse.com>
To: 7eggert@gmx.de
Cc: Eric Dumazet <dada1@cosmosbay.com>,
ReiserFS List <reiserfs-list@namesys.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] reiserfs: fix handling of device names with /'s in them
Date: Fri, 14 Jul 2006 13:50:51 -0400 [thread overview]
Message-ID: <44B7D97B.20708@suse.com> (raw)
In-Reply-To: <E1G1QFx-0001IO-K6@be1.lrz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bodo Eggert wrote:
> Eric Dumazet <dada1@cosmosbay.com> wrote:
>> On Wednesday 12 July 2006 18:42, Jeff Mahoney wrote:
>
>>> On systems with block devices containing slashes (virtual dasd, cciss,
>>> etc), reiserfs will fail to initialize /proc/fs/reiserfs/<dev> due to
>>> it being interpreted as a subdirectory. The generic block device code
>>> changes the / to ! for use in the sysfs tree. This patch uses that
>>> convention.
>>>
>>> Tested by making dm devices use dm/<number> rather than dm-<number>
>> Your patch handles at most one slash. But the description mentions 'slashes'
>> (ie several slashes)
>
> Besides that, there is no reason to prevent the user from using many slashes.
> OTOH, I'd prefer propper quoting, but having each driver do this would be
> insane.
The strings aren't user-supplied, they're kernel-internal names of block
devices, supplied by the driver. At present there is no possibility of
more than one slash in the name, and I doubt we'll see any new devices
with one slash in them, never mind more than one.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFEt9l6LPWxlyuTD7IRAgwsAJ9nvPJRnnJsbqukhtJj3T2mjJC1hQCfYYeh
lbTYktc+yglYRmxT/LwPcT4=
=767A
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-14 17:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6xQ4C-6NB-43@gated-at.bofh.it>
[not found] ` <6xQea-6ZX-13@gated-at.bofh.it>
2006-07-14 16:10 ` [PATCH] reiserfs: fix handling of device names with /'s in them Bodo Eggert
2006-07-14 17:50 ` Jeff Mahoney [this message]
2006-07-16 7:12 ` Hans Reiser
2006-07-16 15:56 ` Jeffrey Mahoney
2006-07-16 18:14 ` Hans Reiser
2006-07-16 22:17 ` Jeff Mahoney
2006-07-17 1:21 ` Hans Reiser
2006-07-17 1:50 ` Jeffrey Mahoney
2006-07-17 3:02 ` Hans Reiser
2006-07-17 3:17 ` Jeffrey Mahoney
2006-07-17 7:29 ` Hans Reiser
2006-07-17 14:55 ` Jeff Mahoney
2006-07-17 15:39 ` Carlos Carvalho
2006-07-17 16:05 ` Jeff Mahoney
2006-07-17 18:21 ` Hans Reiser
2006-07-17 18:19 ` Hans Reiser
2006-07-17 18:38 ` Jeff Mahoney
2006-07-17 19:07 ` Hans Reiser
2006-07-17 19:59 ` Jeff Mahoney
2006-07-17 21:03 ` Hans Reiser
2006-07-17 22:26 ` Rudy Zijlstra
2006-07-18 0:26 ` Horst von Brand
2006-07-18 16:38 ` Jan Engelhardt
2006-07-18 18:37 ` Pekka Enberg
2006-07-17 18:08 ` Valdis.Kletnieks
2006-07-17 18:16 ` Jeff Mahoney
2006-07-17 18:53 ` Hans Reiser
2006-07-17 19:07 ` Jeff Mahoney
2006-07-17 18:27 ` Hans Reiser
2006-07-17 19:52 ` Valdis.Kletnieks
2006-07-12 16:42 Jeff Mahoney
2006-07-12 16:57 ` Eric Dumazet
2006-07-12 17:02 ` Jeff Mahoney
2006-07-13 0:55 ` Andrew Morton
2006-07-13 3:51 ` Hans Reiser
2006-07-13 4:00 ` Andrew Morton
2006-07-13 7:34 ` Hans Reiser
2006-07-13 5:23 ` H. Peter Anvin
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=44B7D97B.20708@suse.com \
--to=jeffm@suse.com \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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 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.