general protection fault in preempt_schedule_notrace_thunk

4 views
Skip to first unread message

syzbot

unread,
Sep 16, 2020, 11:42:16 AM9/16/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 729e3d09 Merge tag 'ceph-for-5.9-rc5' of git://github.com/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13c80bed900000
kernel config: https://syzkaller.appspot.com/x/.config?x=c61610091f4ca8c4
dashboard link: https://syzkaller.appspot.com/bug?extid=155553f1de9b06f3c5d8
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ak...@linux-foundation.org jro...@suse.de linux-...@vger.kernel.org nixia...@huawei.com pet...@infradead.org v...@virtuozzo.com]

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+155553...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 1 PID: 22631 Comm: syz-executor.3 Not tainted 5.9.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:preempt_schedule_notrace_thunk+0x5/0x31 arch/x86/entry/thunk_64.S:41
Code: 00 48 8d a0 58 ff ff ff e8 e9 04 46 00 55 48 89 e5 57 56 52 51 50 41 50 41 51 41 52 41 53 e8 a3 d5 f5 06 eb 18 55 48 89 e5 57 <00> 70 07 00 41 50 41 51 41 52 41 53 e8 eb d5 f5 06 eb 00 41 5b 41
RSP: 0018:ffffc90008f57690 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: 1ffffffff1308b21
RDX: 1ffff11013024365 RSI: 0000000000000001 RDI: ffffffff89bbd540
RBP: ffffc90008f57698 R08: 0000000000000000 R09: ffffffff8134482e
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: ffff888098121b28
FS: 00007f3c2f98c700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000008 CR3: 000000003d050000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0x3b5/0xae0 kernel/locking/lockdep.c:4980
down_read_trylock kernel/locking/rwsem.c:1520 [inline]
down_read_trylock+0x193/0x350 kernel/locking/rwsem.c:1515
mmap_read_trylock include/linux/mmap_lock.h:56 [inline]
do_user_addr_fault+0x25e/0xbf0 arch/x86/mm/fault.c:1313
handle_page_fault arch/x86/mm/fault.c:1429 [inline]
exc_page_fault+0xa8/0x190 arch/x86/mm/fault.c:1482
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:538
RIP: 0010:preempt_schedule_notrace_thunk+0x5/0x31 arch/x86/entry/thunk_64.S:41
Code: 00 48 8d a0 58 ff ff ff e8 e9 04 46 00 55 48 89 e5 57 56 52 51 50 41 50 41 51 41 52 41 53 e8 a3 d5 f5 06 eb 18 55 48 89 e5 57 <00> 70 07 00 41 50 41 51 41 52 41 53 e8 eb d5 f5 06 eb 00 41 5b 41
RSP: 0018:ffffc90008f57988 EFLAGS: 00010246
RAX: 0000000000000001 RBX: 0000000000000001 RCX: 1ffffffff1308b21
RDX: dffffc0000000000 RSI: ffffffff89bd6980 RDI: 0000000000000282
RBP: ffffc90008f57990 R08: 0000000000000000 R09: ffffffff8ab26c0f
R10: fffffbfff1564d81 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff89bd6a40 R14: ffffffff814e6415 R15: dffffc0000000000
rcu_read_unlock_sched_notrace include/linux/rcupdate.h:772 [inline]
trace_lock_release include/trace/events/lock.h:58 [inline]
lock_release+0x634/0x8f0 kernel/locking/lockdep.c:5017
rcu_lock_release include/linux/rcupdate.h:246 [inline]
rcu_read_unlock include/linux/rcupdate.h:688 [inline]
__atomic_notifier_call_chain+0xe7/0x180 kernel/notifier.c:174
do_con_write+0x46d/0x1d70 drivers/tty/vt/vt.c:2900
con_write+0x22/0xb0 drivers/tty/vt/vt.c:3250
process_output_block drivers/tty/n_tty.c:595 [inline]
n_tty_write+0x3ce/0xf80 drivers/tty/n_tty.c:2333
do_tty_write drivers/tty/tty_io.c:962 [inline]
tty_write+0x4d9/0x870 drivers/tty/tty_io.c:1046
vfs_write+0x2b0/0x730 fs/read_write.c:576
ksys_write+0x12d/0x250 fs/read_write.c:631
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d5f9
Code: 5d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f3c2f98bc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000038980 RCX: 000000000045d5f9
RDX: 0000000000001006 RSI: 0000000020001440 RDI: 0000000000000007
RBP: 000000000118d020 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cfec
R13: 000000000169fb6f R14: 00007f3c2f98c9c0 R15: 000000000118cfec
Modules linked in:
---[ end trace 1b8993935343c174 ]---
RIP: 0010:preempt_schedule_notrace_thunk+0x5/0x31 arch/x86/entry/thunk_64.S:41
Code: 00 48 8d a0 58 ff ff ff e8 e9 04 46 00 55 48 89 e5 57 56 52 51 50 41 50 41 51 41 52 41 53 e8 a3 d5 f5 06 eb 18 55 48 89 e5 57 <00> 70 07 00 41 50 41 51 41 52 41 53 e8 eb d5 f5 06 eb 00 41 5b 41
RSP: 0018:ffffc90008f57690 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: 1ffffffff1308b21
RDX: 1ffff11013024365 RSI: 0000000000000001 RDI: ffffffff89bbd540
RBP: ffffc90008f57698 R08: 0000000000000000 R09: ffffffff8134482e
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: ffff888098121b28
FS: 00007f3c2f98c700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000008 CR3: 000000003d050000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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

unread,
Dec 11, 2020, 10:37:09 AM12/11/20
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages