From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Gabriel C <nix.or.die@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Peter Anvin <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ruslan Ruslichenko <rruslich@cisco.com>,
stable@vger.kernel.org, alan@linux.intel.com
Subject: Re: [patch 1/2] x86/platform/goldfish: Prevent unconditional loading
Date: Wed, 15 Feb 2017 11:53:01 +0100 [thread overview]
Message-ID: <20170215105301.GB6557@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170215102145.074836404@linutronix.de>
On Wed, Feb 15, 2017 at 11:11:50AM +0100, Thomas Gleixner wrote:
> The goldfish platform code registers the platform device unconditionally
> which causes havoc in several ways if the goldfish_pdev_bus driver is
> enabled:
>
> - Access to the hardcoded physical memory region, which is either not
> available or contains stuff which is completely unrelated.
>
> - Prevents that the interrupt of the serial port can be requested
>
> - In case of a spurious interrupt it goes into a infinite loop in the
> interrupt handler of the pdev_bus driver (which needs to be fixed
> seperately).
>
> Add a 'goldfish' command line option to make the registration opt-in when
> the platform is compiled in.
>
> I'm seriously grumpy about this engineering trainwreck, which has seven
> SOBs from Intel developers for 50 lines of code. And none of them figured
> out that this is broken. Impressive fail!
>
> Fixes: ddd70cf93d78 ("goldfish: platform device for x86")
> Reported-by: Gabriel C <nix.or.die@gmail.com>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: stable@vger.kernel.org
Just thinking, could we not simply delete this entire driver and use
x86-DT support to setup this platform?
next prev parent reply other threads:[~2017-02-15 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 10:11 [patch 0/2] goldfish: Prevent the trainwreck from doing harm Thomas Gleixner
2017-02-15 10:11 ` [patch 1/2] x86/platform/goldfish: Prevent unconditional loading Thomas Gleixner
2017-02-15 10:53 ` Peter Zijlstra [this message]
2017-02-15 10:57 ` Thomas Gleixner
2017-02-15 12:17 ` Alan Cox
2017-02-15 14:52 ` Thomas Gleixner
2017-02-15 10:11 ` [patch 2/2] goldfish: Sanitize the broken interrupt handler Thomas Gleixner
2017-02-15 15:49 ` [patch 0/2] goldfish: Prevent the trainwreck from doing harm Linus Torvalds
2017-02-15 16:52 ` Greg Kroah-Hartman
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=20170215105301.GB6557@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alan@linux.intel.com \
--cc=bp@alien8.de \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nix.or.die@gmail.com \
--cc=rruslich@cisco.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®