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]

Date:	Wed, 30 Aug 2006 23:04:56 -0400
From:	Shaya Potter <spotter@...columbia.edu>
To:	Matthew Wilcox <matthew@....cx>
Cc:	John Stoffel <john@...ffel.org>, Greg KH <greg@...ah.com>,
	Christoph Hellwig <hch@...radead.org>,
	David Howells <dhowells@...hat.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	zippel@...ux-m68k.org
Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block
	layer [try #2]

On Wed, 2006-08-30 at 21:01 -0600, Matthew Wilcox wrote:
> On Tue, Aug 29, 2006 at 05:08:46PM -0400, John Stoffel wrote:
> > Maybe the better solution is to remove SCSI as an option, and to just
> > offer SCSI drivers and USB-STORAGE and other SCSI core using drivers
> > instead.  Then the SCSI core gets pulled in automatically.  It's not
> > like people care about the SCSI core, just the drivers which depend on
> > it.
> 
> People don't want to have to say "no" to umpteen scsi drivers.  They
> just want to say "no" to SCSI, because they know they don't have scsi.

so then that's shows a problem with the kconfig syntax.

CONFIG_SCSI should perhaps be hidden, and what's visible to the user is
CONFIG_SCSI_DRIVER

USB-STORAGE would automatically pull in CONFIG_SCSI as would
CONFIG_SCSI_DRIVER.

or perhaps I'm just talking out of my ass.

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