From: Xi Ruoyao <xry111@xry111.site>
To: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
libc-alpha@sourceware.org
Subject: Strange EFAULT on mips64el returned by syscall when another thread is forking
Date: Wed, 24 Jan 2024 18:42:30 +0800 [thread overview]
Message-ID: <75e9fd7b08562ad9b456a5bdaacb7cc220311cc9.camel@xry111.site> (raw)
Hi,
When I'm testing Glibc master branch for upcoming 2.39 release, I
noticed an alarming test failure on mips64el:
FAIL: stdlib/tst-arc4random-thread
I've gathered some info about it and pasted my findings into
https://sourceware.org/glibc/wiki/Testing/Tests/stdlib/tst-arc4random-thread.
Finally I was able to reduce the test case into:
#include <stdlib.h>
#include <errno.h>
#include <pthread.h>
#include <unistd.h>
#include <fcntl.h>
void *
test_thread (void *)
{
char buf[16] = {};
int fd = open("/dev/zero", O_RDONLY);
while (1)
{
ssize_t ret = read (fd, buf, 7);
if (ret == -1 && errno == EFAULT)
abort ();
}
}
void *
fork_thread (void *)
{
while (1)
{
if (!fork ())
_exit (0);
}
}
int
main (void)
{
pthread_t test_th;
pthread_t fork_th;
pthread_create (&test_th, NULL, test_thread, NULL);
pthread_create (&fork_th, NULL, fork_thread, NULL);
pthread_join (test_th, NULL);
pthread_join (fork_th, NULL);
}
When running this on the mainline kernel (revision 6.8.0-rc1+-
g7ed2632ec7d72e926b9e8bcc9ad1bb0cd37274bf) it fails in milliseconds.
Some "interesting" aspects:
1. This is related to the size parameter passed to read (). When it's
less than 8 it fails, but when it's 8 or greater there is no failure.
2. This is not related to if "buf" is initialized or not.
Now I'm suspecting this might be a kernel bug. Any pointer to further
triage?
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next reply other threads:[~2024-01-24 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 10:42 Xi Ruoyao [this message]
2024-01-24 11:59 ` Strange EFAULT on mips64el returned by syscall when another thread is forking 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
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=75e9fd7b08562ad9b456a5bdaacb7cc220311cc9.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=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).