public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: Noah Goldstein via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v1] x86: Fix bug in strncmp-evex and strncmp-avx2 [BZ #28895]
Date: Tue, 15 Feb 2022 18:04:53 +0100	[thread overview]
Message-ID: <874k50m56y.fsf@igel.home> (raw)
In-Reply-To: <CAFUsyfJYGRFtJBO5=mpD-nwqiKzSAxB9jxRKC2W7Jzh9F560SA@mail.gmail.com> (Noah Goldstein's message of "Tue, 15 Feb 2022 10:49:06 -0600")

On Feb 15 2022, Noah Goldstein wrote:

> On Tue, Feb 15, 2022 at 10:48 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
>>
>> On Feb 15 2022, Noah Goldstein via Libc-alpha wrote:
>>
>> > diff --git a/string/test-strncmp.c b/string/test-strncmp.c
>> > index 831cb77893..501055de0c 100644
>> > --- a/string/test-strncmp.c
>> > +++ b/string/test-strncmp.c
>> > @@ -423,6 +423,29 @@ check3 (void)
>> >       }
>> >  }
>> >
>> > +
>> > +static void
>> > +check4 (void)
>> > +{
>> > +  /* To trigger bug 28895; We need 1) both s1 and s2 to be within 32 bytes of
>> > +     the end of the page. 2) For there to be no mismatch/null byte before the
>> > +     first page cross. 3) For length (`n`) to be large enough for one string to
>> > +     cross the page. And 4) for there to be either mismatch/null bytes before
>> > +     the start of the strings.  */
>> > +
>> > +  size_t size = 10;
>> > +  CHAR *s1 = (CHAR *)(buf1 + (getpagesize () & 0xffa) / sizeof (CHAR));
>> > +  CHAR *s2 = (CHAR *)(buf2 + (getpagesize () & 0xfed) / sizeof (CHAR));
>>
>> s/&/-/
> ?

(0x1000 & 0xffa) == 0

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2022-02-15 17:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 16:28 Noah Goldstein
2022-02-15 16:32 ` H.J. Lu
2022-02-15 16:42   ` Noah Goldstein
2022-02-15 16:44     ` H.J. Lu
2022-02-15 16:42 ` [PATCH v2] " Noah Goldstein
2022-02-15 16:45   ` H.J. Lu
2022-02-15 16:48 ` [PATCH v1] " Andreas Schwab
2022-02-15 16:49   ` Noah Goldstein
2022-02-15 17:04     ` Andreas Schwab [this message]
2022-02-15 17:24       ` Noah Goldstein
2022-02-15 17:23 ` [PATCH v3] " Noah Goldstein
2022-02-15 18:11   ` Andreas Schwab
2022-02-16  2:27 ` [PATCH v4] " Noah Goldstein
2022-02-16  2:28   ` H.J. Lu
2022-05-04  6:02     ` Sunil Pandey

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=874k50m56y.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=goldstein.w.n@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).