linux-kernel - Re: [GIT PULL] x86/platform changes for v3.9

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130220111255.GB26252@8bytes.org>
Date:	Wed, 20 Feb 2013 12:12:55 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] x86/platform changes for v3.9

On Wed, Feb 20, 2013 at 10:02:38AM +0100, Ingo Molnar wrote:
> Timers and APIC would be my leading suspect - but scheduler and 
> hotplug changes might be the culprits as well.
> 
> Yesterday, while preparing the trees I wanted to mention this 
> x86/apic commit:
> 
>   336224ba5e4f x86, apic: Mask IO-APIC and PIC unconditionally on LAPIC resume
> 
> ... as a change that needs monitored because it changes the 
> suspend and shutdown sequence but then skipped mentioning it 
> because it seemed relatively old and proven.

Hmm, this commit only touches the resume-path. I would wonder if this
has something to do with reboot, can't rule it out, though.

> But there are other potentially dangerous commits as well - I 
> suspect we won't be able to avoid a bisection :-/

Yes, I think a bisection would be best if the problem is reproducible.


	Joerg


--
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/