From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Gabriel C <nix.or.die@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Peter Anvin <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
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
Subject: [patch 0/2] goldfish: Prevent the trainwreck from doing harm
Date: Wed, 15 Feb 2017 11:11:49 +0100 [thread overview]
Message-ID: <20170215101149.937286619@linutronix.de> (raw)
The goldfish android emulator platform is a complete trainwreck which
causes havoc when enabled in Kconfig.
Aside of unconditionally registering a platform device with hardcoded
address ranges, it prevents the serial interrupt from being requested and
in case of a spurious interrupt the broken interrupt handler of the
pdev_bus driver goes into a hard to debug infinite loop.
Thanks to Gabriel and Borislav for providing patiently debug information.
No thanks to the folks @Intel who choked this $corporate trainwreck down
our throat and wasted the time of everyone who got bitten by this.
Thanks,
tglx
next reply other threads:[~2017-02-15 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 10:11 Thomas Gleixner [this message]
2017-02-15 10:11 ` [patch 1/2] x86/platform/goldfish: Prevent unconditional loading Thomas Gleixner
2017-02-15 10:53 ` Peter Zijlstra
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=20170215101149.937286619@linutronix.de \
--to=tglx@linutronix.de \
--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=peterz@infradead.org \
--cc=rruslich@cisco.com \
--cc=stable@vger.kernel.org \
--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