From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Teck Choon Giam <giamteckchoon@gmail.com>, gregkh@linuxfoundation.org
Cc: Greg KH <gregkh@linuxfoundation.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
stable@vger.kernel.org
Subject: Re: Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please.
Date: Tue, 3 Apr 2012 10:31:14 -0400 [thread overview]
Message-ID: <20120403143114.GA27326@phenom.dumpdata.com> (raw)
In-Reply-To: <CAEwRVpNMZaQq0vaoS0aLk2rv3ysyhtOpXKub9HWR0bosgku6_Q@mail.gmail.com>
On Tue, Apr 03, 2012 at 10:26:42PM +0800, Teck Choon Giam wrote:
> On Tue, Apr 3, 2012 at 9:28 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >> > Author: Suresh Siddha <suresh.b.siddha@intel.com>
> >> > Date: Mon Mar 12 11:36:33 2012 -0700
> >> >
> >> > x86/ioapic: Add register level checks to detect bogus io-apic entries
> >> >
> >> > With out this commit, if the bios lists bogus io-apic's, then we will
> >> > see some error messages ("Unable to reset IRR for apic")during linux
> >> > boot which are benign. But as this patch breaks Xen, I am ok if these
> >> > don't get applied to 'stable'. Also I think it is Ingo who added the
> >> > 'stable' tag. Ingo, are you ok with this?
> >>
> >> What stable trees did this already go into in the releases today?
> >
> > I see it in v3.2.x as:
> > 273fb19 x86/ioapic: Add register level checks to detect bogus io-apic entries
> >
> > And in 3.0.x:
> > c2ec63e x86/ioapic: Add register level checks to detect bogus io-apic entries
>
> And does this also affect 3.3.x? I haven't test but guess it will?
Yup!
>
> # git log | grep -B 5 'x86/ioapic: Add register level checks to detect
> bogus io-apic entries'
>
> commit a998dc2fa76f496d2944f0602b920d1d10d7467d
> Author: Suresh Siddha <suresh.b.siddha@intel.com>
> Date: Mon Mar 12 11:36:33 2012 -0700
>
> x86/ioapic: Add register level checks to detect bogus io-apic entries
>
Greg, please also revert this one.
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Teck Choon Giam <giamteckchoon@gmail.com>, gregkh@linuxfoundation.org
Cc: Greg KH <gregkh@linuxfoundation.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
stable@vger.kernel.org
Subject: Re: Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please.
Date: Tue, 3 Apr 2012 10:31:14 -0400 [thread overview]
Message-ID: <20120403143114.GA27326@phenom.dumpdata.com> (raw)
In-Reply-To: <CAEwRVpNMZaQq0vaoS0aLk2rv3ysyhtOpXKub9HWR0bosgku6_Q@mail.gmail.com>
On Tue, Apr 03, 2012 at 10:26:42PM +0800, Teck Choon Giam wrote:
> On Tue, Apr 3, 2012 at 9:28 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >> > Author: Suresh Siddha <suresh.b.siddha@intel.com>
> >> > Date: � Mon Mar 12 11:36:33 2012 -0700
> >> >
> >> > � � x86/ioapic: Add register level checks to detect bogus io-apic entries
> >> >
> >> > With out this commit, if the bios lists bogus io-apic's, then we will
> >> > see some error messages ("Unable to reset IRR for apic")during linux
> >> > boot which are benign. But as this patch breaks Xen, I am ok if these
> >> > don't get applied to 'stable'. Also I think it is Ingo who added the
> >> > 'stable' tag. Ingo, are you ok with this?
> >>
> >> What stable trees did this already go into in the releases today?
> >
> > I see it in v3.2.x as:
> > 273fb19 x86/ioapic: Add register level checks to detect bogus io-apic entries
> >
> > And in 3.0.x:
> > c2ec63e x86/ioapic: Add register level checks to detect bogus io-apic entries
>
> And does this also affect 3.3.x? I haven't test but guess it will?
Yup!
>
> # git log | grep -B 5 'x86/ioapic: Add register level checks to detect
> bogus io-apic entries'
>
> commit a998dc2fa76f496d2944f0602b920d1d10d7467d
> Author: Suresh Siddha <suresh.b.siddha@intel.com>
> Date: Mon Mar 12 11:36:33 2012 -0700
>
> x86/ioapic: Add register level checks to detect bogus io-apic entries
>
Greg, please also revert this one.
next prev parent reply other threads:[~2012-04-03 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 22:47 Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please Konrad Rzeszutek Wilk
2012-04-02 23:02 ` Suresh Siddha
2012-04-02 23:27 ` Greg KH
2012-04-02 23:43 ` Suresh Siddha
2012-04-02 23:49 ` Greg KH
2012-04-03 13:04 ` Konrad Rzeszutek Wilk
2012-04-03 13:28 ` Konrad Rzeszutek Wilk
2012-04-03 14:26 ` Teck Choon Giam
2012-04-03 14:26 ` Teck Choon Giam
2012-04-03 14:31 ` Konrad Rzeszutek Wilk [this message]
2012-04-03 14:31 ` Konrad Rzeszutek Wilk
2012-04-03 14:56 ` Teck Choon Giam
2012-04-03 14:56 ` Teck Choon Giam
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=20120403143114.GA27326@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=giamteckchoon@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@vger.kernel.org \
--cc=suresh.b.siddha@intel.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.