lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44BB0146.7080702@suse.com>
Date:	Sun, 16 Jul 2006 23:17:26 -0400
From:	Jeffrey Mahoney <jeffm@...e.com>
To:	Hans Reiser <reiser@...esys.com>
Cc:	7eggert@....de, Eric Dumazet <dada1@...mosbay.com>,
	ReiserFS List <reiserfs-list@...esys.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] reiserfs: fix handling of device names with /'s in them

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans Reiser wrote:
> Jeffrey Mahoney wrote:
>> This is not
>> the desired interpretation, which is why we need to replace the pathname
>> separator in the name. ReiserFS is the component that is choosing to use
>> the block device name as a pathname component and is responsible for
>> making any translation to that usage.
> 
> This makes no sense.  I have the feeling you see trees and I see forest.

No, Hans. I see a problem that has been fixed elsewhere in an identical
manner. The real solution is to eliminate / from block devices in the
long run, not to start introducing mount points with different pathname
interpretation rules. Those may have a place elsewhere, after a tough
uphill battle, and are most certainly overkill for this problem.

- -Jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEuwFFLPWxlyuTD7IRAsiiAJ9cwTuov+2OM7GI44L1wQ/XDBMy9ACeIIYQ
5xEIRCQXHAZFG7oOFEkWJS4=
=onBb
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ