From: Andreas Schwab <schwab@suse.de>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: Noah Goldstein <goldstein.w.n@gmail.com>,
Carlos O'Donell <carlos@redhat.com>,
hjl.tools@gmail.com, carlos@systemhalted.org
Subject: Re: [PATCH v1] x86: Prevent SIG11 in memcmp-sse2 when data is concurrently modified [BZ #29863]
Date: Wed, 14 Dec 2022 10:04:26 +0100 [thread overview]
Message-ID: <mvmcz8ms6ed.fsf@suse.de> (raw)
In-Reply-To: <8dc9f68a-c736-0996-76f8-ab7aeb4ccc00@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Tue, 13 Dec 2022 21:41:36 -0500")
On Dez 13 2022, Carlos O'Donell via Libc-alpha wrote:
> Please post a v2. Thanks!
>
> Subject: x86: Prevent SIGSEGV in memcmp-sse2 when data is concurrently modified [BZ #29863]
>
> Replaces SIG11 with SIGSEGV (the documented name of the signal).
Even better: out-of-bounds access (which can manifest in multitude of
different ways).
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-12-14 9:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 0:11 Noah Goldstein
2022-12-14 2:41 ` Carlos O'Donell
2022-12-14 9:04 ` Andreas Schwab [this message]
2022-12-14 3:25 ` [PATCH v2] x86: Prevent SIGSEGV " Noah Goldstein
2022-12-14 4:42 ` Carlos O'Donell
2022-12-14 7:36 ` [PATCH v3] " Noah Goldstein
2022-12-14 16:09 ` H.J. Lu
2022-12-14 16:57 ` Carlos O'Donell
2022-12-14 17:18 ` Noah Goldstein
2022-12-14 18:52 ` Noah Goldstein
2022-12-14 16:57 ` Carlos O'Donell
2022-12-14 16:07 ` [PATCH v1] x86: Prevent SIG11 " H.J. Lu
2022-12-14 18:52 ` [PATCH v4] x86: Prevent SIGSEGV " Noah Goldstein
2022-12-14 21:35 ` H.J. Lu
2023-01-10 22:02 ` Sunil Pandey
2023-01-10 23:02 ` Noah Goldstein
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=mvmcz8ms6ed.fsf@suse.de \
--to=schwab@suse.de \
--cc=carlos@redhat.com \
--cc=carlos@systemhalted.org \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).