From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Yinghai Lu <yinghai.lu@amd.com>,
Andi Kleen <ak@suse.de>, Glauber Costa <gcosta@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] [PATCH] x86: Restore proper vector locking during cpu hotplug
Date: Sun, 10 Aug 2008 16:51:57 -0700 [thread overview]
Message-ID: <489F7F1D.3030606@zytor.com> (raw)
In-Reply-To: <m11w0xu9hd.fsf@frodo.ebiederm.org>
Eric W. Biederman wrote:
> Having cpu_online_map change during assign_irq_vector can result
> in some really nasty and weird things happening. The one that
> bit me last time was accessing non existent per cpu memory for non
> existent cpus.
>
> This locking was removed in a sloppy x86_64 and x86_32 merge patch.
>
> Guys can we please try and avoid subtly breaking x86 when we are
> merging files together?
Queuing for tip:x86/urgent.
prev parent reply other threads:[~2008-08-10 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 22:09 [PATCH] [PATCH] x86: Restore proper vector locking during cpu hotplug Eric W. Biederman
2008-08-10 23:51 ` H. Peter Anvin [this message]
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=489F7F1D.3030606@zytor.com \
--to=hpa@zytor.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gcosta@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai.lu@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox