linux-kernel - Re: [git patches] libata updates

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:	Mon, 30 Apr 2007 18:11:42 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Chuck Ebbert <cebbert@...hat.com>
CC:	linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git patches] libata updates

Chuck Ebbert wrote:
> Jeff Garzik wrote:
>> Chuck Ebbert wrote:
>>> Jeff Garzik wrote:
>>>> Jeff Garzik (8):
>>>>       libata/IDE: remove combined mode quirk
>>> You can't just remove the "combined_mode=" kernel parameter or
>>> every Linux user who uses that will get an unbootable kernel
>>> with no good way of diagnosing the problem. It should still
>>> be accepted and just print a warning.
>> No, most modern distros will simply Just Work(tm) due to mount by label,
>> udev, and similar gadgets.
>>
>> As long as you have at least one (if not both) ATA drivers, you have a
>> kernel that will boot your hardware.  And by definition those using
>> combined_mode= do indeed have the necessary drivers.
> 
> OK, this is a kernel parameter and should be fine. But you can't remove
> *module* parameters for drivers needed for booting or the initrd will
> fail to load the module with "unknown parameter" and users can't boot.

No module parameters were removed.

	Jeff



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