From: syzbot <syzbot+fd2f89c6e52024e6118d@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: [syzbot] riscv/fixes test error: BUG: unable to handle kernel paging request in corrupted
Date: Sat, 11 Sep 2021 14:19:16 -0700 [thread overview]
Message-ID: <000000000000c4d45205cbbec87f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7d2a07b76933 Linux 5.14
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=1153e67d300000
kernel config: https://syzkaller.appspot.com/x/.config?x=f8211b06020972e8
dashboard link: https://syzkaller.appspot.com/bug?extid=fd2f89c6e52024e6118d
compiler: riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
userspace arch: riscv64
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+fd2f89c6e52024e6118d@syzkaller.appspotmail.com
Unable to handle kernel paging request at virtual address 1ffffffff07aa547
Oops [#1]
Modules linked in:
CPU: 0 PID: 3309 Comm: kworker/0:5 Not tainted 5.14.0-syzkaller #0
Hardware name: riscv-virtio,qemu (DT)
Workqueue: events nsim_dev_trap_report_work
epc : slab_alloc_node mm/slub.c:2884 [inline]
epc : __kmalloc_node_track_caller+0xb0/0x3d2 mm/slub.c:4653
ra : slab_pre_alloc_hook mm/slab.h:494 [inline]
ra : slab_alloc_node mm/slub.c:2880 [inline]
ra : __kmalloc_node_track_caller+0x70/0x3d2 mm/slub.c:4653
epc : ffffffff803e2a20 ra : ffffffff803e29e0 sp : ffffffe0095c3b20
gp : ffffffff83f967d8 tp : ffffffe00ba397c0 t0 : ffffffe008b544a8
t1 : 0000000000000001 t2 : ffffffffeddd472a s0 : ffffffe0095c3bc0
s1 : ffffffe005602140 a0 : 0000000000000000 a1 : 0000000000000007
a2 : 1ffffffff07aa51f a3 : ffffffff80a9711a a4 : 0000000004000000
a5 : 0000000000000000 a6 : 0000000000f00000 a7 : 78e919c5cf7e2f00
s2 : ffffffff83f96adc s3 : 0000000000082a20 s4 : 0000000000001000
s5 : ffffffffffffffff s6 : ffffffff81538164 s7 : ffffffff83f9a0d0
s8 : 0000000000000000 s9 : 0000000000082a20 s10: 0000000000000000
s11: ffffffe008b545c8 t3 : 78e919c5cf7e2f00 t4 : ffffffc40116a8bb
t5 : ffffffc40116a8bc t6 : ffffffe00eede026
status: 0000000000000120 badaddr: 1ffffffff07aa547 cause: 000000000000000f
[<ffffffff803e2a20>] slab_alloc_node mm/slub.c:2884 [inline]
[<ffffffff803e2a20>] __kmalloc_node_track_caller+0xb0/0x3d2 mm/slub.c:4653
[<ffffffff821a8952>] kmalloc_reserve net/core/skbuff.c:355 [inline]
[<ffffffff821a8952>] __alloc_skb+0xee/0x2e2 net/core/skbuff.c:426
[<ffffffff81538164>] alloc_skb include/linux/skbuff.h:1112 [inline]
[<ffffffff81538164>] nsim_dev_trap_skb_build drivers/net/netdevsim/dev.c:664 [inline]
[<ffffffff81538164>] nsim_dev_trap_report drivers/net/netdevsim/dev.c:721 [inline]
[<ffffffff81538164>] nsim_dev_trap_report_work+0x1cc/0x5e6 drivers/net/netdevsim/dev.c:762
[<ffffffff80063b62>] process_one_work+0x5e0/0xf82 kernel/workqueue.c:2276
[<ffffffff8006485a>] worker_thread+0x356/0x8e6 kernel/workqueue.c:2422
[<ffffffff80076554>] kthread+0x25c/0x2c6 kernel/kthread.c:319
[<ffffffff8000515e>] ret_from_exception+0x0/0x14
---[ end trace fa569262b4bfae4f ]---
---
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-09-11 21:19 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=000000000000c4d45205cbbec87f@google.com \
--to=syzbot+fd2f89c6e52024e6118d@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).