From: Zorro Lang <zlang@redhat.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: bugzilla-daemon@kernel.org, linux-s390@vger.kernel.org,
linux-xfs@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Bug 216073] New: [s390x] kernel BUG at mm/usercopy.c:101! usercopy: Kernel memory exposure attempt detected from vmalloc 'n o area' (offset 0, size 1)!
Date: Thu, 9 Jun 2022 10:49:15 +0800 [thread overview]
Message-ID: <20220609024915.geephkxchu2fgpwk@zlang-mailbox> (raw)
In-Reply-To: <YqD0yAELzHxdRBU6@li-4a3a4a4c-28e5-11b2-a85c-a8d192c6f089.ibm.com>
On Wed, Jun 08, 2022 at 09:13:12PM +0200, Alexander Gordeev wrote:
> On Wed, Jun 08, 2022 at 10:19:22AM +0800, Zorro Lang wrote:
> > One of the test environment details as [1]. The xfstests config as [2].
> > It's easier to reproduce on 64k directory size xfs by running xfstests
> > auto group.
>
>
> Thanks for the details, Zorro!
>
> Do you create test and scratch device with xfs_io, as README suggests?
> If yes, what are sizes of the files?
# fallocate -l 5G /home/test_dev.img
# fallocate -l 10G /home/scratch_dev.img
Then create loop devices.
> Also, do you run always xfs/auto or xfs/294 hits for you reliably?
100% for on my testing, I tried 10 times, then hit it 10 times last
weekend. Will test again this week.
>
> Thanks!
>
next prev parent reply other threads:[~2022-06-09 2:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216073-27@https.bugzilla.kernel.org/>
2022-06-06 22:13 ` [Bug 216073] New: [s390x] kernel BUG at mm/usercopy.c:101! usercopy: Kernel memory exposure attempt detected from vmalloc 'n o area' (offset 0, size 1)! Andrew Morton
2022-06-07 15:05 ` Alexander Gordeev
2022-06-08 2:19 ` Zorro Lang
2022-06-08 19:13 ` Alexander Gordeev
2022-06-09 2:49 ` Zorro Lang [this message]
2022-06-12 4:42 ` Zorro Lang
2022-06-12 11:58 ` Matthew Wilcox
2022-06-12 13:03 ` Uladzislau Rezki
2022-06-12 17:26 ` Matthew Wilcox
2022-06-12 17:59 ` Yu Zhao
2022-06-12 18:05 ` Matthew Wilcox
2022-06-12 18:43 ` Yu Zhao
2022-06-12 19:52 ` Matthew Wilcox
2022-06-12 20:53 ` Yu Zhao
2022-06-12 19:07 ` Uladzislau Rezki
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=20220609024915.geephkxchu2fgpwk@zlang-mailbox \
--to=zlang@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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 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.