linux-kernel - Re: 2.6.28: How come some kernel options cannot be disabled for non-existent hardware?

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] [day] [month] [year] [list]

Message-ID: <20081230131447.GA14942@srcf.ucam.org>
Date:	Tue, 30 Dec 2008 13:14:47 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: 2.6.28: How come some kernel options cannot be disabled for non-existent hardware?

On Tue, Dec 30, 2008 at 07:25:42AM -0500, Justin Piszcz wrote:

> It still shows up as enabled and it is in dmesg shown above.  How come 
> some kernel options are enabled and cannot (easily?) be disabled for 
> hardware that does not exist in my machine?

It's enabled by the ATA_ACPI support so libata can handle ACPI-based 
drive hotswaps. You can check these by looking at the help for an option 
in make menuconfig. That'll tell you what's selecting an option.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/