linux-kernel - Re: [PATCH 3/4] NOMMU: Make it possible for RomFS to use MTD devices directly

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]

Date:	Thu, 19 Feb 2009 16:12:11 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	David Howells <dhowells@...hat.com>
Cc:	dwmw2@...radead.org, bernds_cb1@...nline.de, dhowells@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] NOMMU: Make it possible for RomFS to use MTD
 devices directly

On Thu, 12 Feb 2009 10:40:10 +0000
David Howells <dhowells@...hat.com> wrote:

> Change RomFS so that it can use MTD devices directly - without the intercession
> of the block layer - as well as using block devices.
> 
> This permits RomFS:
> 
>  (1) to use the MTD direct mapping facility available under NOMMU conditions if
>      the underlying device is directly accessible by the CPU (including XIP);
> 
>  (2) and thus to be used when the block layer is disabled.
> 
> RomFS can be configured with support just for MTD devices, just for Block
> devices or for both.  If RomFS is configured for both, then it will treat
> mtdblock device files as MTD backing stores, not block layer backing stores.

My x86_64 usualconfig just exploded with

fs/romfs/storage.c:18:2: error: #error no ROMFS backing store interface configured

http://userweb.kernel.org/~akpm/config-akpm2.txt
--
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/