From: Drake Wilson <drake@dasyatidae.net>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Sami Kerola <kerolasa@iki.fi>, Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 09/10] lscpu: blacklist vmware_bdoor() AddressSanitizer check
Date: Sun, 30 Nov 2014 11:27:58 -0600 [thread overview]
Message-ID: <547B539E.9020902@dasyatidae.net> (raw)
In-Reply-To: <1417365287.1296747.196968317.62A1BE41@webmail.messagingengine.com>
Benno Schulenberg wrote:
> Hmm... How come that it doesn't flag the very similar segment in
> static inline void cpuid(...) as suspicious? Is it the 'inl' command?
> (What does this do anyway? It isn't an x86 assembly that I can find.)
The IN does a read from I/O port space; the "l" suffix in AT&T syntax means
32-bit operand size. I'm guessing AddressSanitizer sees what looks like a
memory reference with 16-bit address size coming from nowhere that should
have a pointer in it and complains. It's not a "real" memory reference,
so ignoring the whole function seems reasonable. (It's very unusual to use
that instruction from userspace, so it's not surprising it wouldn't be
recognized.)
---> Drake Wilson
next prev parent reply other threads:[~2014-11-30 17:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 13:57 [PATCH 00/10] pull: AddressSanitizer round II Sami Kerola
2014-11-30 13:57 ` [PATCH 01/10] lib/mbalign: fix unsigned integer overflow [AddressSanitizer] Sami Kerola
2014-12-03 23:53 ` Pádraig Brady
2014-12-04 20:14 ` Sami Kerola
2014-12-07 11:56 ` Pádraig Brady
2014-12-08 11:00 ` Karel Zak
2014-12-04 11:51 ` Pádraig Brady
2014-11-30 13:57 ` [PATCH 02/10] cal: fix signed " Sami Kerola
2014-12-08 11:07 ` Karel Zak
2014-11-30 13:57 ` [PATCH 03/10] more: fix unsigned " Sami Kerola
2014-12-08 11:42 ` Karel Zak
2014-12-08 12:56 ` Sami Kerola
2014-12-19 9:20 ` Sami Kerola
2014-11-30 13:57 ` [PATCH 04/10] lib: fix crc32 and crc64 interger overflows [AddressSanitizer] Sami Kerola
2014-11-30 13:57 ` [PATCH 05/10] fdisk: (sgi) fix unsigned integer overflow [AddressSanitizer] Sami Kerola
2014-11-30 13:57 ` [PATCH 06/10] strutils: fix unsigned integer overflows [AddressSanitizer] Sami Kerola
2014-11-30 13:57 ` [PATCH 07/10] mkfs.cramfs: fix unsigned integer overflow [AddressSanitizer] Sami Kerola
2014-12-08 11:37 ` Karel Zak
2014-12-19 9:24 ` Sami Kerola
2014-11-30 13:57 ` [PATCH 08/10] include/c: define UL_ASAN_BLACKLIST address_sanitizer function attribute Sami Kerola
2014-11-30 16:42 ` Benno Schulenberg
2014-12-19 9:50 ` Sami Kerola
2014-11-30 13:57 ` [PATCH 09/10] lscpu: blacklist vmware_bdoor() AddressSanitizer check Sami Kerola
2014-11-30 16:34 ` Benno Schulenberg
2014-11-30 17:17 ` Sami Kerola
2014-11-30 17:27 ` Drake Wilson [this message]
2014-11-30 13:57 ` [PATCH 10/10] ipcs: fix two data type errors [AddressSanitizer] Sami Kerola
2014-12-08 12:21 ` Karel Zak
2014-12-19 9:26 ` Sami Kerola
2014-11-30 14:03 ` [PATCH 00/10] pull: AddressSanitizer round II Sami Kerola
2014-12-15 9:15 ` Karel Zak
2014-12-15 10:38 ` Sami Kerola
2014-12-19 9:52 ` Sami Kerola
2014-12-19 13:23 ` Karel Zak
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=547B539E.9020902@dasyatidae.net \
--to=drake@dasyatidae.net \
--cc=bensberg@justemail.net \
--cc=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.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 NNTP newsgroup(s).