From: syzbot <syzbot+66bcf89bc98a2524351b@syzkaller.appspotmail.com>
To: boqun.feng@gmail.com, linux-kernel@vger.kernel.org,
longman@redhat.com, mingo@redhat.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, will@kernel.org
Subject: [syzbot] BUG: sleeping function called from invalid context in do_page_fault (2)
Date: Fri, 30 Apr 2021 13:48:13 -0700 [thread overview]
Message-ID: <000000000000fc85d105c136baf5@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7ae11635 riscv: keep interrupts disabled for BREAKPOINT ex..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=132778c1d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f8af20e245283c9a
dashboard link: https://syzkaller.appspot.com/bug?extid=66bcf89bc98a2524351b
userspace arch: riscv64
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+66bcf89bc98a2524351b@syzkaller.appspotmail.com
BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1352
in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 6832, name: syz-executor.1
Unable to handle kernel paging request at virtual address ffffffe024768000
Oops [#1]
Modules linked in:
CPU: 1 PID: 6832 Comm: syz-executor.1 Not tainted 5.12.0-rc6-syzkaller-00183-g7ae11635ec90 #0
Hardware name: riscv-virtio,qemu (DT)
epc : ___might_sleep+0x21c/0x2c0 kernel/sched/core.c:8317
ra : ___might_sleep+0x21c/0x2c0 kernel/sched/core.c:8317
epc : ffffffe00008456c ra : ffffffe00008456c sp : ffffffe07fdffd90
gp : ffffffe004588ad0 tp : ffffffe008680000 t0 : ffffffe004ffdbb7
t1 : ffffffc40ffbff52 t2 : 0000000000000000 s0 : ffffffe07fdffdd0
s1 : ffffffe024768000 a0 : ffffffe024768000 a1 : 0000000000000007
a2 : 1ffffffc048ed000 a3 : ffffffe00008456c a4 : 0000000000000000
a5 : ffffffe024768000 a6 : 0000000000f00000 a7 : ffffffe07fdffa97
s2 : 0000000000000000 s3 : 0000000000000100 s4 : ffffffe008680000
s5 : ffffffe0000274ec s6 : 0000000000000000 s7 : ffffffe07fdfffe0
s8 : 0000000000000214 s9 : ffffffe0071e4ed8 s10: 0000000000001000
s11: ffffffe003000c68 t3 : dd4b702f2cefd800 t4 : ffffffc40ffbff51
t5 : ffffffc40ffbff53 t6 : ffffffe07fdffa98
status: 0000000000000100 badaddr: ffffffe024768000 cause: 000000000000000d
Call Trace:
[<ffffffe00008456c>] ___might_sleep+0x21c/0x2c0 kernel/sched/core.c:8317
[<ffffffe00008466a>] __might_sleep+0x5a/0x8a kernel/sched/core.c:8282
[<ffffffe002a996ec>] down_read+0x2e/0x1a4 kernel/locking/rwsem.c:1352
[<ffffffe00000fef8>] mmap_read_lock include/linux/mmap_lock.h:117 [inline]
[<ffffffe00000fef8>] do_page_fault+0x1e6/0x95e arch/riscv/mm/fault.c:263
[<ffffffe000005586>] ret_from_exception+0x0/0x14
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2021-04-30 20:48 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=000000000000fc85d105c136baf5@google.com \
--to=syzbot+66bcf89bc98a2524351b@syzkaller.appspotmail.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox