linux-kernel - Re: [Re: 2.6.21-rc2-mm1] #error no ROMFS backing store interface configured

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: <20070304041111.1d2774e7.akpm@linux-foundation.org>
Date:	Sun, 4 Mar 2007 04:11:11 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Maciej Rutecki <maciej.rutecki@...il.com>
Cc:	linux-kernel@...r.kernel.org, dhowells@...hat.com,
	Adrian Bunk <bunk@...sta.de>
Subject: Re: [Re: 2.6.21-rc2-mm1] #error no ROMFS backing store interface
 configured

On Sun, 04 Mar 2007 12:58:39 +0100 Maciej Rutecki <maciej.rutecki@...il.com> wrote:

> CC [M]  fs/romfs/storage.o
> fs/romfs/storage.c:18:2: error: #error no ROMFS backing store interface
> configured
> make[3]: *** [fs/romfs/storage.o] Błąd 1
> make[2]: *** [fs/romfs] Błąd 2
> make[1]: *** [fs] Błąd 2
> make[1]: Opuszczenie katalogu `/usr/src/linux-mm'
> make: *** [debian/stamp-build-kernel] Błąd 2
> 

+config ROMFS_ON_BLOCK
+	bool "Block device-backed ROM file system support"
+	depends on ROMFS_FS && BLOCK
+	help
+	  This permits ROMFS to use block devices buffered through the page
+	  cache as the medium from which to retrieve data.  It does not allow
+	  direct mapping of the medium.
+
+	  If unsure, answer Y.
+
+config ROMFS_ON_MTD
+	bool "MTD-backed ROM file system support"
+	depends on ROMFS_FS && MTD
+	help
+	  This permits ROMFS to use MTD based devices directly, without the
+	  intercession of the block layer (which may have been disabled).  It
+	  also allows direct mapping of MTD devices through romfs files under
+	  NOMMU conditions if the underlying device is directly addressable by
+	  the CPU.
+

So we require that one of these be enabled if ROMFS.

There's a way of doing that, but I forget what it is.  iirc Adrian has done
this in the past and can perhaps point us at an example?
-
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/