From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1B8C63857C5B; Tue, 18 Jan 2022 16:38:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1B8C63857C5B From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/27398] x86: Improve testing false positive for tst-cpu-features-cpuinfo with bad hardware. Date: Tue, 18 Jan 2022 16:38:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.35 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: hjl.tools at gmail dot com X-Bugzilla-Target-Milestone: 2.35 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2022 16:38:21 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27398 --- Comment #18 from Carlos O'Donell --- (In reply to Carlos O'Donell from comment #17) > (In reply to H.J. Lu from comment #16) > > Created attachment 13914 [details] > > The v4 patch > >=20 > > Please try this. >=20 > That works. Extending it to cover 0xc stepping fixes both failures. >=20 > As one of the Intel maintainers for glibc I'm going to rely on your > judgement here if extending the errata to cover 0xc is acceptable. Worst > case this is pessimistic for this hardware and we get user feedback that > they want the range adjusted. Note that Siddhesh's hardware is also stepping 12, so this isn't something random, but a specific flaw with this stepping or a kernel issue. But we can sort out the latter with more time, and blacklisting this CPU seems correct= for now. --=20 You are receiving this mail because: You are on the CC list for the bug.=