linux-kernel - Re: Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 3 Apr 2012 22:56:15 +0800
From:	Teck Choon Giam <giamteckchoon@...il.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	gregkh@...uxfoundation.org,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	linux-kernel@...r.kernel.org, mingo@...e.hu, stable@...r.kernel.org
Subject: Re: Don't apply 9f022e54b8ea82d1ecdf3bd78d9ab9f44d6b0655 to stable please.

On Tue, Apr 3, 2012 at 10:31 PM, Konrad Rzeszutek Wilk
<konrad.wilk@...cle.com> wrote:
> 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@...cle.com> wrote:
>> >> > Author: Suresh Siddha <suresh.b.siddha@...el.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@...el.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.

I will include the various tree commit id as below:

linux-3.0.y:
commit c2ec63edaf48c90c3495eeb0b75bb05102fbf71a
Author: Suresh Siddha <suresh.b.siddha@...el.com>
Date:   Mon Mar 12 11:36:33 2012 -0700

    x86/ioapic: Add register level checks to detect bogus io-apic entries

linux-3.1.y: Don't have such commit and I guess it is due to EOL before Mar 12

linux-3.2.y:
commit 273fb194e86b795b08a724c7646d0f694949070b
Author: Suresh Siddha <suresh.b.siddha@...el.com>
Date:   Mon Mar 12 11:36:33 2012 -0700

    x86/ioapic: Add register level checks to detect bogus io-apic entries

linux-3.3.y:
commit a998dc2fa76f496d2944f0602b920d1d10d7467d
Author: Suresh Siddha <suresh.b.siddha@...el.com>
Date:   Mon Mar 12 11:36:33 2012 -0700

    x86/ioapic: Add register level checks to detect bogus io-apic entries


Thanks.

Kindest regards,
Giam Teck Choon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/