From: Xi Ruoyao <xry111@xry111.site>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
libc-alpha@sourceware.org
Subject: Re: Strange EFAULT on mips64el returned by syscall when another thread is forking
Date: Wed, 24 Jan 2024 20:49:06 +0800 [thread overview]
Message-ID: <9481b6d9d015aea25d8f2563bf7bd6f6462f758f.camel@xry111.site> (raw)
In-Reply-To: <mvmplxraqmd.fsf@suse.de>
On Wed, 2024-01-24 at 12:59 +0100, Andreas Schwab wrote:
> On Jan 24 2024, Xi Ruoyao wrote:
>
> > Now I'm suspecting this might be a kernel bug. Any pointer to further
> > triage?
>
> Is this a regression?
Initially I guessed it was perhaps a Glibc regression related to the
newly introduced clone3 usage on MIPS, but it fails with Glibc-2.35 too.
Not sure if this is a kernel regression, I'll try different kernels in
several hours (once I can physically access the system).
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-01-24 12:49 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 [this message]
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
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=9481b6d9d015aea25d8f2563bf7bd6f6462f758f.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=schwab@suse.de \
--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 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 NNTP newsgroup(s).