INFO: task hung in path_openat (3)
9 views
Skip to first unread message
syzbot
Aug 11, 2022, 9:14:24 AM8/11/22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f7ec2d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=ecb1a957408fd20bf401
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
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+ecb1a9...@syzkaller.appspotmail.com
overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off.
INFO: task syz-executor.5:5112 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.5 D29744 5112 8108 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
__rwsem_down_read_failed_common kernel/locking/rwsem-xadd.c:292 [inline]
rwsem_down_read_failed+0x20a/0x390 kernel/locking/rwsem-xadd.c:309
call_rwsem_down_read_failed+0x14/0x30 arch/x86/lib/rwsem.S:94
__down_read arch/x86/include/asm/rwsem.h:83 [inline]
down_read+0x44/0x80 kernel/locking/rwsem.c:26
inode_lock_shared include/linux/fs.h:758 [inline]
do_last fs/namei.c:3326 [inline]
path_openat+0x17ec/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f0e45848279
Code: Bad RIP value.
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
RSP: 002b:00007f0e4417b168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f0e4595b120 RCX: 00007f0e45848279
VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop0.
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000
audit: type=1804 audit(1660223602.440:4609): pid=14344 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir3036540135/syzkaller.7RroPq/1344/file0/bus" dev="sda1" ino=14174 res=1
RBP: 00007f0e458a2189 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
audit: type=1804 audit(1660223602.500:4610): pid=14354 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.0" name="/root/syzkaller-testdir3036540135/syzkaller.7RroPq/1344/file0/bus" dev="sda1" ino=14174 res=1
R13: 00007fff292b981f R14: 00007f0e4417b300 R15: 0000000000022000
INFO: task syz-executor.5:5125 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
syz-executor.5 D29744 5125 8108 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
__rwsem_down_read_failed_common kernel/locking/rwsem-xadd.c:292 [inline]
rwsem_down_read_failed+0x20a/0x390 kernel/locking/rwsem-xadd.c:309
VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop0.
call_rwsem_down_read_failed+0x14/0x30 arch/x86/lib/rwsem.S:94
audit: type=1804 audit(1660223602.840:4611): pid=14379 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir3036540135/syzkaller.7RroPq/1345/file0/bus" dev="sda1" ino=14277 res=1
__down_read arch/x86/include/asm/rwsem.h:83 [inline]
down_read+0x44/0x80 kernel/locking/rwsem.c:26
inode_lock_shared include/linux/fs.h:758 [inline]
do_last fs/namei.c:3326 [inline]
path_openat+0x17ec/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f0e45848279
Code: Bad RIP value.
RSP: 002b:00007f0e4415a168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f0e4595b1f0 RCX: 00007f0e45848279
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000
RBP: 00007f0e458a2189 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff292b981f R14: 00007f0e4415a300 R15: 0000000000022000
Showing all locks held in the system:
1 lock held by khungtaskd/1571:
#0: 00000000636ef489 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7803:
#0: 00000000f55ef5ba (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
2 locks held by syz-executor.2/8105:
#0: 0000000096d52b55 (&bdev->bd_mutex){+.+.}, at: __blkdev_put+0xfc/0x870 fs/block_dev.c:1806
#1: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: lo_release+0x1a/0x1f0 drivers/block/loop.c:1790
2 locks held by syz-executor.1/8109:
#0: 000000003f7ce36d (&bdev->bd_mutex){+.+.}, at: __blkdev_put+0xfc/0x870 fs/block_dev.c:1806
#1: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: __loop_clr_fd+0x88/0xe50 drivers/block/loop.c:1080
2 locks held by syz-executor.3/27045:
#0: 000000008847c04c (&bdev->bd_mutex){+.+.}, at: __blkdev_put+0xfc/0x870 fs/block_dev.c:1806
#1: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: __loop_clr_fd+0x777/0xe50 drivers/block/loop.c:1164
2 locks held by syz-executor.5/5104:
1 lock held by syz-executor.5/5112:
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: inode_lock_shared include/linux/fs.h:758 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: do_last fs/namei.c:3326 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: path_openat+0x17ec/0x2df0 fs/namei.c:3537
1 lock held by syz-executor.5/5125:
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: inode_lock_shared include/linux/fs.h:758 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: do_last fs/namei.c:3326 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: path_openat+0x17ec/0x2df0 fs/namei.c:3537
1 lock held by syz-executor.4/14405:
#0: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: loop_set_fd drivers/block/loop.c:956 [inline]
#0: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: lo_ioctl+0x1bb/0x20e0 drivers/block/loop.c:1576
2 locks held by systemd-udevd/14407:
#0: 000000008847c04c (&bdev->bd_mutex){+.+.}, at: __blkdev_get+0x1d0/0x1480 fs/block_dev.c:1478
#1: 00000000fca24d17 (&(&parent->list_lock)->rlock){-.-.}, at: kernfs_seq_start+0x4b/0x260 fs/kernfs/file.c:112
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1571 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 9434 Comm: kworker/u4:7 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: bat_events batadv_nc_worker
RIP: 0010:__lock_acquire+0x3d9/0x3ff0 kernel/locking/lockdep.c:3359
Code: 85 46 28 00 00 48 8b 84 24 d8 01 00 00 49 8d 7a 10 48 89 fa 48 c1 ea 03 49 89 42 08 48 b8 00 00 00 00 00 fc ff df 80 3c 02 00 <0f> 85 43 28 00 00 48 b8 00 00 00 00 00 fc ff df 4d 89 72 10 4d 8d
RSP: 0018:ffff88805a267a68 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 000000000000002e
RDX: 1ffff1100b44b1dd RSI: 1ffff1100b44b1da RDI: ffff88805a258ee8
RBP: 0000000000000002 R08: 000000000000002e R09: 0000000000000002
R10: ffff88805a258ed8 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88805a258600 R14: ffffffff89f85fa0 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055e7311d9988 CR3: 00000000901b4000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
rcu_lock_acquire include/linux/rcupdate.h:242 [inline]
rcu_read_lock include/linux/rcupdate.h:627 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:419 [inline]
batadv_nc_worker+0x12d/0xd50 net/batman-adv/network-coding.c:730
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f7ec2d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=ecb1a957408fd20bf401
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
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+ecb1a9...@syzkaller.appspotmail.com
overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off.
INFO: task syz-executor.5:5112 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.5 D29744 5112 8108 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
__rwsem_down_read_failed_common kernel/locking/rwsem-xadd.c:292 [inline]
rwsem_down_read_failed+0x20a/0x390 kernel/locking/rwsem-xadd.c:309
call_rwsem_down_read_failed+0x14/0x30 arch/x86/lib/rwsem.S:94
__down_read arch/x86/include/asm/rwsem.h:83 [inline]
down_read+0x44/0x80 kernel/locking/rwsem.c:26
inode_lock_shared include/linux/fs.h:758 [inline]
do_last fs/namei.c:3326 [inline]
path_openat+0x17ec/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f0e45848279
Code: Bad RIP value.
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
RSP: 002b:00007f0e4417b168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f0e4595b120 RCX: 00007f0e45848279
VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop0.
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000
audit: type=1804 audit(1660223602.440:4609): pid=14344 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir3036540135/syzkaller.7RroPq/1344/file0/bus" dev="sda1" ino=14174 res=1
RBP: 00007f0e458a2189 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
audit: type=1804 audit(1660223602.500:4610): pid=14354 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.0" name="/root/syzkaller-testdir3036540135/syzkaller.7RroPq/1344/file0/bus" dev="sda1" ino=14174 res=1
R13: 00007fff292b981f R14: 00007f0e4417b300 R15: 0000000000022000
INFO: task syz-executor.5:5125 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
xt_cluster: you have exceeded the maximum number of cluster nodes (300 > 32)
syz-executor.5 D29744 5125 8108 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
__rwsem_down_read_failed_common kernel/locking/rwsem-xadd.c:292 [inline]
rwsem_down_read_failed+0x20a/0x390 kernel/locking/rwsem-xadd.c:309
VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop0.
call_rwsem_down_read_failed+0x14/0x30 arch/x86/lib/rwsem.S:94
audit: type=1804 audit(1660223602.840:4611): pid=14379 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir3036540135/syzkaller.7RroPq/1345/file0/bus" dev="sda1" ino=14277 res=1
__down_read arch/x86/include/asm/rwsem.h:83 [inline]
down_read+0x44/0x80 kernel/locking/rwsem.c:26
inode_lock_shared include/linux/fs.h:758 [inline]
do_last fs/namei.c:3326 [inline]
path_openat+0x17ec/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f0e45848279
Code: Bad RIP value.
RSP: 002b:00007f0e4415a168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f0e4595b1f0 RCX: 00007f0e45848279
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000
RBP: 00007f0e458a2189 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff292b981f R14: 00007f0e4415a300 R15: 0000000000022000
Showing all locks held in the system:
1 lock held by khungtaskd/1571:
#0: 00000000636ef489 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7803:
#0: 00000000f55ef5ba (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
2 locks held by syz-executor.2/8105:
#0: 0000000096d52b55 (&bdev->bd_mutex){+.+.}, at: __blkdev_put+0xfc/0x870 fs/block_dev.c:1806
#1: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: lo_release+0x1a/0x1f0 drivers/block/loop.c:1790
2 locks held by syz-executor.1/8109:
#0: 000000003f7ce36d (&bdev->bd_mutex){+.+.}, at: __blkdev_put+0xfc/0x870 fs/block_dev.c:1806
#1: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: __loop_clr_fd+0x88/0xe50 drivers/block/loop.c:1080
2 locks held by syz-executor.3/27045:
#0: 000000008847c04c (&bdev->bd_mutex){+.+.}, at: __blkdev_put+0xfc/0x870 fs/block_dev.c:1806
#1: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: __loop_clr_fd+0x777/0xe50 drivers/block/loop.c:1164
2 locks held by syz-executor.5/5104:
1 lock held by syz-executor.5/5112:
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: inode_lock_shared include/linux/fs.h:758 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: do_last fs/namei.c:3326 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: path_openat+0x17ec/0x2df0 fs/namei.c:3537
1 lock held by syz-executor.5/5125:
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: inode_lock_shared include/linux/fs.h:758 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: do_last fs/namei.c:3326 [inline]
#0: 00000000ae1a7ed9 (&type->i_mutex_dir_key#9){++++}, at: path_openat+0x17ec/0x2df0 fs/namei.c:3537
1 lock held by syz-executor.4/14405:
#0: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: loop_set_fd drivers/block/loop.c:956 [inline]
#0: 000000004e5ef39a (loop_ctl_mutex){+.+.}, at: lo_ioctl+0x1bb/0x20e0 drivers/block/loop.c:1576
2 locks held by systemd-udevd/14407:
#0: 000000008847c04c (&bdev->bd_mutex){+.+.}, at: __blkdev_get+0x1d0/0x1480 fs/block_dev.c:1478
#1: 00000000fca24d17 (&(&parent->list_lock)->rlock){-.-.}, at: kernfs_seq_start+0x4b/0x260 fs/kernfs/file.c:112
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1571 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 9434 Comm: kworker/u4:7 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: bat_events batadv_nc_worker
RIP: 0010:__lock_acquire+0x3d9/0x3ff0 kernel/locking/lockdep.c:3359
Code: 85 46 28 00 00 48 8b 84 24 d8 01 00 00 49 8d 7a 10 48 89 fa 48 c1 ea 03 49 89 42 08 48 b8 00 00 00 00 00 fc ff df 80 3c 02 00 <0f> 85 43 28 00 00 48 b8 00 00 00 00 00 fc ff df 4d 89 72 10 4d 8d
RSP: 0018:ffff88805a267a68 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 000000000000002e
RDX: 1ffff1100b44b1dd RSI: 1ffff1100b44b1da RDI: ffff88805a258ee8
RBP: 0000000000000002 R08: 000000000000002e R09: 0000000000000002
R10: ffff88805a258ed8 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88805a258600 R14: ffffffff89f85fa0 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055e7311d9988 CR3: 00000000901b4000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
rcu_lock_acquire include/linux/rcupdate.h:242 [inline]
rcu_read_lock include/linux/rcupdate.h:627 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:419 [inline]
batadv_nc_worker+0x12d/0xd50 net/batman-adv/network-coding.c:730
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Reply all
Reply to author
Forward
0 new messages