linux-kernel - Re: [PATCH] Subject: [PATCH] x86, AMD: K8 Rev.A-E processors are subject to erratum 400

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: <20110429202338.GA21523@aftab>
Date:	Fri, 29 Apr 2011 22:23:38 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Boris Ostrovsky <boris.ostrovsky@....com>
Cc:	Ingo Molnar <mingo@...e.hu>, Boris Ostrovsky <ostr@...64.org>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"jvpeetz@....de" <jvpeetz@....de>
Subject: Re: [PATCH] Subject: [PATCH] x86, AMD: K8 Rev.A-E processors are
 subject to erratum 400

On Fri, Apr 29, 2011 at 04:11:26PM -0400, Boris Ostrovsky wrote:
> On 04/29/2011 03:55 PM, Ingo Molnar wrote:
> >
> > * Boris Ostrovsky<ostr@...64.org>  wrote:
> >
> >> Signed-off-by: Boris Ostrovsky<Boris.Ostrovsky@....com>
> >> Acked-by: Borislav Petkov<borislav.petkov@....com>
> >> Reported-by: Joerg-Volker Peetz<jvpeetz@....de>
> >> Tested-by: Joerg-Volker Peetz<jvpeetz@....de>
> >>
> >> Older AMD K8 processors (Revisions A-E) are affected by erratum 400 (APIC
> >> timer interrupts don't occur in C states greater than C1). This, for example,
> >> means that X86_FEATURE_ARAT flag should not be set for these parts.
> >>
> >> This addresses regression introduced by commit
> >> b87cf80af3ba4b4c008b4face3c68d604e1715c6 (x86, AMD: Set ARAT feature on AMD
> >> processors") so it is somewhat high priority.
> >
> > Hm, what is the regression, how do users see it? Hangs? Delays? Crashes?
> > Something more benign? The changelog should really contain such information.
> 
> 
> The system becomes unresponsive until an external interrupt (e.g. 
> keyboard input) happens. The most obvious effect is that time is not 
> reported correctly. We haven't seen anything worse but that's probably 
> bad enough.
> 
> Do you want me to resubmit the patch with updated comments?

Yes please. Being too verbose is much better than being laconic with the
commit message.

Also, please put those lines

Signed-off-by: Boris Ostrovsky <Boris.Ostrovsky@....com>
Acked-by: Borislav Petkov <borislav.petkov@....com>
Reported-by: Joerg-Volker Peetz <jvpeetz@....de>
Tested-by: Joerg-Volker Peetz <jvpeetz@....de>

_after_ the commit message.

Thanks.

-- 
Regards/Gruss,
Boris.

Operating Systems Research Center
Advanced Micro Devices, Inc.
--
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/