Hello,
syzbot found the following issue on:
HEAD commit: 92edc4ae Add linux-next specific files for 20201113
git tree: linux-next
console output:
https://syzkaller.appspot.com/x/log.txt?x=11cd4fbe500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=79ad4f8ad2d96176
dashboard link:
https://syzkaller.appspot.com/bug?extid=eeb3d03618bf784ed400
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [
linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]
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+eeb3d0...@syzkaller.appspotmail.com
INFO: task syz-executor.1:18964 can't die for more than 143 seconds.
task:syz-executor.1 state:D stack:29632 pid:18964 ppid: 8476 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:4269 [inline]
__schedule+0x890/0x2030 kernel/sched/core.c:5019
schedule+0xcf/0x270 kernel/sched/core.c:5098
rwsem_down_read_slowpath+0x328/0xc90 kernel/locking/rwsem.c:1099
__down_read kernel/locking/rwsem.c:1341 [inline]
down_read+0x1ec/0x420 kernel/locking/rwsem.c:1494
iterate_supers+0xdb/0x290 fs/super.c:692
ksys_sync+0x86/0x150 fs/sync.c:114
__do_sys_sync+0xa/0x10 fs/sync.c:125
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45deb9
Code: Unable to access opcode bytes at RIP 0x45de8f.
RSP: 002b:00007fcdd2ecbc78 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00000000000352c0 RCX: 000000000045deb9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000000000118bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007ffdad4bd16f R14: 00007fcdd2ecc9c0 R15: 000000000118bf2c
Showing all locks held in the system:
1 lock held by khungtaskd/1656:
#0: ffffffff8b339ce0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6252
2 locks held by syz-executor.0/14179:
#0: ffff8880726580e0 (&type->s_umount_key#72/1){+.+.}-{3:3}, at: alloc_super+0x201/0xaf0 fs/super.c:229
#1: ffff8880165bc0e0 (&type->s_umount_key#73){++++}-{3:3}, at: grab_super+0x59/0x260 fs/super.c:389
2 locks held by syz-executor.0/14215:
#0: ffff8880165bc0e0 (&type->s_umount_key#72/1){+.+.}-{3:3}, at: alloc_super+0x201/0xaf0 fs/super.c:229
#1: ffff888070e14090 (&client->mount_mutex){+.+.}-{3:3}, at: ceph_real_mount fs/ceph/super.c:924 [inline]
#1: ffff888070e14090 (&client->mount_mutex){+.+.}-{3:3}, at: ceph_get_tree+0x702/0x1750 fs/ceph/super.c:1093
1 lock held by syz-executor.1/18964:
#0: ffff8880165bc0e0 (&type->s_umount_key#73){++++}-{3:3}, at: iterate_supers+0xdb/0x290 fs/super.c:692
=============================================
---
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.