From: Jeff Mahoney <jeffm@suse.com>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: ReiserFS List <reiserfs-list@namesys.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] reiserfs: fix handling of device names with /'s in them
Date: Mon, 17 Jul 2006 12:05:33 -0400 [thread overview]
Message-ID: <44BBB54D.1000509@suse.com> (raw)
In-Reply-To: <17595.44857.845209.442959@fisica.ufpr.br>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Carlos Carvalho wrote:
> Shouldn't the replacement of / by some other character be done for all
> filesystems? If so shouldn't it be done in a single point for all of
> them? Isn't this the purpose of VFS?
This only applies to a corner case where the file system wants to use
the block device name as a pathname. In any other case, interpreting the
/ as a path separator would be the correct behavior. While a helper
function/macro may be appropriate, I don't think the VFS has any
business interpreting names automatically like that.
As stated before numerous times by both Andrew and myself, the correct
solution is to eliminate / from block device names. This patch was a
band-aid until that's done.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFEu7VNLPWxlyuTD7IRAinwAJ43vf+NHkI/U/sA743174o68xw5UQCfaL1z
N367ixvf/HeQuWHZH0CkjVY=
=4+dh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-17 16:05 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
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 [this message]
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=44BBB54D.1000509@suse.com \
--to=jeffm@suse.com \
--cc=akpm@osdl.org \
--cc=carlos@fisica.ufpr.br \
--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.