From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Mark Salter <msalter@redhat.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
rth@twiddle.net, vgupta@synopsys.com, linux@arm.linux.org.uk,
tony.luck@intel.com, geert@linux-m68k.org, monstr@monstr.eu,
ralf@linux-mips.org, jejb@parisc-linux.org,
benh@kernel.crashing.org, lethal@linux-sh.org,
davem@davemloft.net, cmetcalf@tilera.com, gxt@mprc.pku.edu.cn,
tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH] Kconfig cleanup (PARPORT_PC dependencies)
Date: Thu, 12 Sep 2013 13:55:39 -0700 [thread overview]
Message-ID: <52322A4B.9050205@zytor.com> (raw)
In-Reply-To: <20130912205349.GC3262@gmail.com>
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
next prev parent reply other threads:[~2013-09-12 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 18:53 [PATCH] Kconfig cleanup (PARPORT_PC dependencies) Mark Salter
2013-09-12 19:04 ` Chris Metcalf
2013-09-12 19:04 ` Chris Metcalf
2013-09-12 19:19 ` Mark Salter
2013-09-12 19:11 ` Geert Uytterhoeven
2013-09-12 19:13 ` Richard Henderson
2013-09-12 20:07 ` H. Peter Anvin
2013-09-12 20:53 ` Ingo Molnar
2013-09-12 20:55 ` H. Peter Anvin [this message]
2013-09-12 20:32 ` Sam Ravnborg
2013-09-12 20:49 ` Russell King - ARM Linux
2013-09-12 21:21 ` Mark Salter
2013-09-13 16:40 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52322A4B.9050205@zytor.com \
--to=hpa@zytor.com \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=jejb@parisc-linux.org \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=msalter@redhat.com \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vgupta@synopsys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.