From: Florian Weimer <fweimer@redhat.com>
To: GNU C Library <libc-alpha@sourceware.org>,
"H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: SIGBUS failure for misc/tst-bz21269 on i386
Date: Wed, 28 Mar 2018 17:47:00 -0000 [thread overview]
Message-ID: <4b34706e-b156-9ecd-f730-96fb28e38852@redhat.com> (raw)
In-Reply-To: <20180328173657.GA3586@aurel32.net>
On 03/28/2018 07:36 PM, Aurelien Jarno wrote:
> I confirm that this patch works. It returns no error with the fixed
> libc, and a segmentation one with the previous one without the bz21269
> fix.
I reviewed the bug again, and I don't think it will interfere with the
test objective, so I'm going to commit this soon unless someone objects.
Thanks,
Florian
prev parent reply other threads:[~2018-03-28 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 13:35 Florian Weimer
2018-03-14 13:44 ` H.J. Lu
2018-03-14 16:47 ` Adhemerval Zanella
2018-03-27 21:47 ` Aurelien Jarno
2018-03-27 21:58 ` H.J. Lu
2018-03-28 6:47 ` Aurelien Jarno
2018-03-28 8:01 ` Florian Weimer
2018-03-28 17:37 ` Aurelien Jarno
2018-03-28 17:47 ` Florian Weimer [this message]
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=4b34706e-b156-9ecd-f730-96fb28e38852@redhat.com \
--to=fweimer@redhat.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).