general protection fault in process_one_work (2)

6 views
Skip to first unread message

syzbot

unread,
Jul 23, 2021, 8:35:24 AM7/23/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c1a6d08348fc Add linux-next specific files for 20210715
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1793845c300000
kernel config: https://syzkaller.appspot.com/x/.config?x=5ef73f190e4b0b9a
dashboard link: https://syzkaller.appspot.com/bug?extid=ae236c2e559557e598b9
CC: [boqun...@gmail.com linux-...@vger.kernel.org lon...@redhat.com mi...@redhat.com pet...@infradead.org wi...@kernel.org]

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+ae236c...@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: 31787 Comm: kworker/1:17 Tainted: G W 5.14.0-rc1-next-20210715-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: ipv6_addrconf addrconf_dad_work
RIP: 0010:debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline]
RIP: 0010:do_raw_spin_lock+0x69/0x2b0 kernel/locking/spinlock_debug.c:112
Code: 5b 81 48 8d 14 03 c7 02 f1 f1 f1 f1 c7 42 04 04 f3 f3 f3 48 89 fa 65 48 8b 0c 25 28 00 00 00 48 89 4c 24 60 31 c9 48 c1 ea 03 <0f> b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 db
RSP: 0018:ffffc9000a107c90 EFLAGS: 00010047
RAX: dffffc0000000000 RBX: 1ffff92001420f93 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8d6c7817
R10: fffffbfff1ad8f02 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ed22000 CR3: 000000014af55000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
process_one_work+0xad7/0x1630 kernel/workqueue.c:2304
worker_thread+0x658/0x11f0 kernel/workqueue.c:2422
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Modules linked in:
---[ end trace 14bfcb6cde880456 ]---
RIP: 0010:debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline]
RIP: 0010:do_raw_spin_lock+0x69/0x2b0 kernel/locking/spinlock_debug.c:112
Code: 5b 81 48 8d 14 03 c7 02 f1 f1 f1 f1 c7 42 04 04 f3 f3 f3 48 89 fa 65 48 8b 0c 25 28 00 00 00 48 89 4c 24 60 31 c9 48 c1 ea 03 <0f> b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 db
RSP: 0018:ffffc9000a107c90 EFLAGS: 00010047
RAX: dffffc0000000000 RBX: 1ffff92001420f93 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8d6c7817
R10: fffffbfff1ad8f02 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ed22000 CR3: 000000014af55000 CR4: 00000000001506e0
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,
Sep 17, 2021, 8:34:27 AM9/17/21
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