[an error occurred while processing this directive]

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: <20090414070314.GB29075@linux-sh.org>
Date:	Tue, 14 Apr 2009 16:03:14 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Adrian McMenamin <adrian@...golddream.dyndns.info>
Cc:	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-sh <linux-sh@...r.kernel.org>,
	Josef 'Jeff' Sipek <jeffpc@...efsipek.net>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [RFC][patch] filesystem: Vmufat filesystem, version 4

On Tue, Apr 14, 2009 at 08:00:29AM +0100, Adrian McMenamin wrote:
> On Tue, 2009-04-14 at 06:59 +0900, Paul Mundt wrote:
> 
> > This file system is tied directly to the VMU. Assumptions about the
> > on-disk format, block numbering limitations, etc. are all VMU
> > constraints, and papering over that in the Kconfig text is not
> > sufficient. This file system is and always will be tied to the VMU, and
> > you really do not want to decouple the two. What you do in loopback mode
> > for testing is your own business, but this will not work in the way
> > people expect on a fixed disk. You are only making things harder on
> > yourself by insisting that this is somehow generic.
> > 
> > The file system at least wants a dependency on the VMU (and I suppose
> > mtdblock) itself.
> 
> Why won't it work on a fixed disk "in the way people expect"? Granted
> they'd be eccentric to format a disk in this way but there is no
> inherent reason why this file system *has* to be tied to a VMU.
> 
Everything about the on-disk format is tied to the VMU. Until that sinks
in, don't bother sending me email, thanks.
--
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/