From: syzbot <syzbot+d07c65298d2c15eafcb0@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING: locking bug in hugetlb_no_page
Date: Sun, 13 Nov 2022 12:30:27 -0800 [thread overview]
Message-ID: <000000000000511de505ed5ffe6a@google.com> (raw)
In-Reply-To: <20221113115249.1845-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted
rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P3507 } 2668 jiffies s: 2069 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: 1621b6ea Merge branch 'for-next/fixes' into for-kernelci
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=108ca515880000
kernel config: https://syzkaller.appspot.com/x/.config?x=606e57fd25c5c6cc
dashboard link: https://syzkaller.appspot.com/bug?extid=d07c65298d2c15eafcb0
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=174f46d1880000
next parent reply other threads:[~2022-11-13 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221113115249.1845-1-hdanton@sina.com>
2022-11-13 20:30 ` syzbot [this message]
[not found] <20221113055842.1710-1-hdanton@sina.com>
2022-11-13 10:09 ` [syzbot] WARNING: locking bug in hugetlb_no_page syzbot
[not found] <20221113031619.1536-1-hdanton@sina.com>
2022-11-13 4:41 ` syzbot
2022-11-12 14:03 syzbot
2022-11-13 15:36 ` Dmitry Vyukov
2022-11-13 18:50 ` Mike Kravetz
2022-11-14 2:24 ` Mike Kravetz
2022-11-14 9:59 ` Dmitry Vyukov
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=000000000000511de505ed5ffe6a@google.com \
--to=syzbot+d07c65298d2c15eafcb0@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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