public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12077] strncmp over-reads its buffer, may cause SIGSEGV
Date: Fri, 01 Oct 2010 17:14:00 -0000	[thread overview]
Message-ID: <20101001171411.29387.qmail@sourceware.org> (raw)
In-Reply-To: <20101001120105.12077.ppluzhnikov@google.com>


------- Additional Comments From ppluzhnikov at google dot com  2010-10-01 17:14 -------
On SSE4_2 capable machine:

model name      : Intel(R) Xeon(R) CPU           X5550  @ 2.67GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr dca sse4_1 sse4_2 popcnt lahf_lm ida

the test does not crash for any combination of parameters, so __strncmp_sse42
does not have the bug.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=12077

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-10-01 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 12:01 [Bug libc/12077] New: " ppluzhnikov at google dot com
2010-10-01 12:04 ` [Bug libc/12077] " ppluzhnikov at google dot com
2010-10-01 13:23 ` drepper dot fsp at gmail dot com
2010-10-01 14:01 ` ppluzhnikov at google dot com
2010-10-01 17:14 ` ppluzhnikov at google dot com [this message]
2010-10-03  3:12 ` drepper dot fsp at gmail dot com
2010-10-03  3:23 ` ppluzhnikov at google dot com
2010-10-04  2:11 ` drepper dot fsp 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=20101001171411.29387.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).