[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52322A4B.9050205@zytor.com>
Date: Thu, 12 Sep 2013 13:55:39 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Ingo Molnar <mingo@...nel.org>
CC: Mark Salter <msalter@...hat.com>, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org, rth@...ddle.net, vgupta@...opsys.com,
linux@....linux.org.uk, tony.luck@...el.com, geert@...ux-m68k.org,
monstr@...str.eu, ralf@...ux-mips.org, jejb@...isc-linux.org,
benh@...nel.crashing.org, lethal@...ux-sh.org, davem@...emloft.net,
cmetcalf@...era.com, gxt@...c.pku.edu.cn, tglx@...utronix.de,
mingo@...hat.com
Subject: Re: [PATCH] Kconfig cleanup (PARPORT_PC dependencies)
On 09/12/2013 01:53 PM, Ingo Molnar wrote:
>>
>> I'm somewhat astonished that this driver is that problematic. It is
>> really just a very basic PIO interface, at least in the absence of
>> EPP/ECP.
>>
>> It is, of course, also largely a dead interface at this point so it
>> probably doesn't matter.
>
> So, my collection of 'randconfig kernel crashers' has this exclusion and
> comment:
>
> --- linux.orig/drivers/block/Kconfig
> +++ linux/drivers/block/Kconfig
> @@ -77,6 +77,11 @@ config GDROM
> config PARIDE
> tristate "Parallel port IDE device support"
> depends on PARPORT_PC
> +
> + # the probe can hang during bootup on non-PARIDE boxes
> + depends on BROKEN_BOOT_ALLOWED
> + select BROKEN_BOOT if PARIDE = y
> +
>
> So at least some uses of PARPORT_PC are unsafe. (might easily be a bug in
> PARIDE)
>
That I would believe.
-hpa
--
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/
Powered by blists - more mailing lists