public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pageexec at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17259] New: sysdeps/x86_64/cacheinfo.c:intel_check_word corrupts rbx and another register
Date: Mon, 11 Aug 2014 23:29:00 -0000 [thread overview]
Message-ID: <bug-17259-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17259
Bug ID: 17259
Summary: sysdeps/x86_64/cacheinfo.c:intel_check_word corrupts
rbx and another register
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: pageexec at gmail dot com
CC: drepper.fsp at gmail dot com
the inline asm invoking cpuid tries to save/restore rbx itself but unlike its
i386 version, this one will actually corrupt (zero out) the top 32 bits of both
rbx and whatever register gets assigned to %1 due to the "xchg ebx,%1". this
code was probably simply copy-pasted from the i386 version. note that the same
file actually contains a proper implementation of cpuid as the __cpuid_count
macro that had been there some 2 years before this new and buggy 'invention'.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-08-11 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 23:29 pageexec at gmail dot com [this message]
2014-08-12 16:04 ` [Bug libc/17259] sysdeps/x86_64/cacheinfo.c:intel_check_word may corrupt rbx hjl.tools at gmail dot com
2014-08-13 0:06 ` cvs-commit at gcc dot gnu.org
2014-08-13 0:07 ` hjl.tools at gmail dot com
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=bug-17259-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).