linux-kernel - Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]

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: <20060901163403.GC18276@stusta.de>
Date:	Fri, 1 Sep 2006 18:34:03 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Jörn Engel <joern@...nheim.fh-wedel.de>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	David Woodhouse <dwmw2@...radead.org>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	Roman Zippel <zippel@...ux-m68k.org>,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	David Howells <dhowells@...hat.com>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]

On Fri, Sep 01, 2006 at 06:19:20PM +0200, Jörn Engel wrote:
> On Fri, 1 September 2006 17:31:51 +0200, Stefan Richter wrote:
> > 
> > Yes and no. In the latter case, they have to magically know that at
> > least menuconfig and xconfig can be tricked to list depending options.
> 
> True.  Marginally better than horrible then. :)
> 
> > Could be a fun project [...]
> 
> Absolutely.  Assuming that select gets removed in the process, and
> concentrating on oldconfig, would it be enough to have something like
> this in the .config?
> 
> # CONFIG_USB_STORAGE has unmet dependencies: CONFIG_SCSI, CONFIG_BLOCK
> 
> Now people looking for usb mass storage can find the option without
> grepping through Kconfig files, but also every single driver for every
> single disabled subsystem shows up.  Might be a bit too much.

Common use case:
A driver was changed to use FW_LOADER.
The .config for the old kernel contains CONFIG_FW_LOADER=n.
The user runs "make oldconfig" with the old .config in the new kernel.

How do you plan to handle this reasonably without select?

> Jörn

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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