linux-kernel - Re: [PATCH] reiserfs: fix handling of device names with /'s in them

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: <44BB3C42.1060309@namesys.com>
Date:	Mon, 17 Jul 2006 00:29:06 -0700
From:	Hans Reiser <reiser@...esys.com>
To:	Jeffrey Mahoney <jeffm@...e.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

Jeffrey Mahoney wrote:

> 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


I don't understand your patch and cannot support it as it is written.  
Perhaps you can call me and explain it on the phone.

Hans
-
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/