From: Xi Ruoyao <xry111@xry111.site>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
libc-alpha@sourceware.org, regressions@lists.linux.dev
Subject: Re: Strange EFAULT on mips64el returned by syscall when another thread is forking
Date: Fri, 26 Jan 2024 20:58:16 +0800 [thread overview]
Message-ID: <1e1ec730efc58f17ecf008a4600321e3d200ebda.camel@xry111.site> (raw)
In-Reply-To: <4b715c9f-6a9e-4496-8810-670080cb715a@app.fastmail.com>
On Fri, 2024-01-26 at 12:33 +0000, Jiaxun Yang wrote:
>
>
> 在2024年1月24日一月 上午10:42，Xi Ruoyao写道：
> > Hi,
> >
> > When I'm testing Glibc master branch for upcoming 2.39 release, I
> > noticed an alarming test failure on mips64el:
>
> So apparently it should be tracked as a regression.
>
> #regzbot ^introduced 4bce37a68ff884e821a02a731897a8119e0c37b7
>
> Should we revert it for now?
I'd say "yes" if we cannot easily patch instruction_pointer() to handle
delay slot. Anyway the reversion will be a MIPS-only change.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-01-26 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 10:42 Strange EFAULT on mips64el returned by syscall when another thread is forking Xi Ruoyao
2024-01-24 11:59 ` Andreas Schwab
2024-01-24 12:49 ` Xi Ruoyao
2024-01-24 16:13 ` Xi Ruoyao
2024-01-24 21:32 ` Xi Ruoyao
2024-01-24 21:38 ` Xi Ruoyao
2024-01-24 21:54 ` Linus Torvalds
2024-01-24 22:10 ` Linus Torvalds
2024-01-24 22:42 ` Xi Ruoyao
2024-01-25 9:28 ` Jiaxun Yang
2024-01-26 12:33 ` Jiaxun Yang
2024-01-26 12:58 ` Xi Ruoyao [this message]
2024-01-26 18:00 ` Xi Ruoyao
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=1e1ec730efc58f17ecf008a4600321e3d200ebda.camel@xry111.site \
--to=xry111@xry111.site \
--cc=jiaxun.yang@flygoat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.