public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goldstein.w.n at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/29088] On x86_64 all versions of memrchr can segfault with seemingly valid inputs.
Date: Sun, 24 Apr 2022 22:51:17 +0000 [thread overview]
Message-ID: <bug-29088-131-Mfmkgvqotz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29088-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29088
--- Comment #3 from Noah Goldstein <goldstein.w.n at gmail dot com> ---
(In reply to Andreas Schwab from comment #2)
> "Where an argument declared as size_t n specifies the length of the array
> for a function, n can have the value zero on a call to that function.
> Unless explicitly stated otherwise in the description of a particular
> function in this subclause, pointer arguments on such a call shall still
> have valid values, as described in 7.1.4."
I see. `Test - 0` SSE2 bug is not a bug then.
Does 'pointer arguments on such a call shall still have valid values' imply a
certain amount of memory that must be valid or just a single byte? If its just
a single byte the second bug is still a bug as each of them over-reads into a
vector register.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-24 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 20:43 [Bug string/29088] New: " goldstein.w.n at gmail dot com
2022-04-24 20:45 ` [Bug string/29088] " goldstein.w.n at gmail dot com
2022-04-24 22:27 ` schwab@linux-m68k.org
2022-04-24 22:51 ` goldstein.w.n at gmail dot com [this message]
2022-07-14 11:12 ` schwab@linux-m68k.org
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-29088-131-Mfmkgvqotz@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).