From: Jeffrey Bastian <jbastian@redhat.com>
To: linux-mm@kvack.org
Subject: stress-ng procfs test triggers kernel bug in mm/usercopy.c
Date: Wed, 28 Oct 2020 13:39:15 -0500 [thread overview]
Message-ID: <20201028183915.pn74yxbggmpdujge@tarantula.users.ipa.redhat.com> (raw)
I just opened a BZ for "kernel BUG at mm/usercopy.c:99!" while running
the stress-ng procfs stressor on the 5.10.0-rc1 kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=209919
It's easily reproducible on x86_64 and arm64 (aarch64) systems. I'm
testing on ppc64le and s390x next.
--
Jeff Bastian
Kernel QE - Hardware Enablement
Red Hat
reply other threads:[~2020-10-28 18:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201028183915.pn74yxbggmpdujge@tarantula.users.ipa.redhat.com \
--to=jbastian@redhat.com \
--cc=linux-mm@kvack.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