general protection fault in bond_alb_monitor

12 views
Skip to first unread message

syzbot

unread,
May 17, 2021, 7:40:23 AM5/17/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d2b6f8a1 Merge tag 'xfs-5.13-merge-3' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b4afb9d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=53fdf14defd48c56
dashboard link: https://syzkaller.appspot.com/bug?extid=82cebdc33bd391b84521
compiler: Debian clang version 11.0.1-2
CC: [an...@greyhouse.net da...@davemloft.net j.vos...@gmail.com ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org vfa...@gmail.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+82cebd...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xdffffc0000000016: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7]
CPU: 0 PID: 189 Comm: kworker/u4:5 Not tainted 5.12.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bond30 bond_alb_monitor
RIP: 0010:list_empty include/linux/list.h:282 [inline]
RIP: 0010:bond_alb_monitor+0xb7/0x1690 drivers/net/bonding/bond_alb.c:1533
Code: e8 03 48 89 44 24 20 42 80 3c 28 00 48 89 3c 24 74 09 e8 2c 58 c5 fc 48 8b 3c 24 bb b0 00 00 00 48 03 1f 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 0a 58 c5 fc 48 8b 03 48 39 d8 74
RSP: 0018:ffffc9000133fb40 EFLAGS: 00010202
RAX: 0000000000000016 RBX: 00000000000000b0 RCX: ffff888012c00000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888000124c00
RBP: ffffc9000133fc50 R08: ffffffff815379e3 R09: fffffbfff1c2cd1e
R10: fffffbfff1c2cd1e R11: 0000000000000000 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff888000124fb0 R15: ffffc9000133fd20
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056084572c970 CR3: 0000000147ad4000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
process_one_work+0x833/0x10c0 kernel/workqueue.c:2275
worker_thread+0xac1/0x1300 kernel/workqueue.c:2421
kthread+0x39a/0x3c0 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
Modules linked in:
---[ end trace 7a9014a226e1e061 ]---
RIP: 0010:list_empty include/linux/list.h:282 [inline]
RIP: 0010:bond_alb_monitor+0xb7/0x1690 drivers/net/bonding/bond_alb.c:1533
Code: e8 03 48 89 44 24 20 42 80 3c 28 00 48 89 3c 24 74 09 e8 2c 58 c5 fc 48 8b 3c 24 bb b0 00 00 00 48 03 1f 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 0a 58 c5 fc 48 8b 03 48 39 d8 74
RSP: 0018:ffffc9000133fb40 EFLAGS: 00010202
RAX: 0000000000000016 RBX: 00000000000000b0 RCX: ffff888012c00000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888000124c00
RBP: ffffc9000133fc50 R08: ffffffff815379e3 R09: fffffbfff1c2cd1e
R10: fffffbfff1c2cd1e R11: 0000000000000000 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff888000124fb0 R15: ffffc9000133fd20
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056084572c970 CR3: 0000000081dc5000 CR4: 00000000001506f0
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,
Jul 31, 2021, 8:02:42 PM7/31/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