general protection fault in batadv_iv_ogm_schedule_buff (2)

4 views
Skip to first unread message

syzbot

unread,
Sep 12, 2021, 8:13:18 AM9/12/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b172b44fcb17 Linux 4.19.206
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1044f3b9300000
kernel config: https://syzkaller.appspot.com/x/.config?x=b9ba3521ce0be3cd
dashboard link: https://syzkaller.appspot.com/bug?extid=7a97706650fb860b61c4
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+7a9770...@syzkaller.appspotmail.com

BTRFS error (device loop1): superblock checksum mismatch
BTRFS error (device loop1): open_ctree failed
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 12065 Comm: kworker/u4:4 Not tainted 4.19.206-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet
RIP: 0010:batadv_iv_ogm_schedule_buff+0xc7e/0x1340 net/batman-adv/bat_iv_ogm.c:1026
Code: 80 3c 38 00 0f 85 be 06 00 00 48 8b 1b 48 81 fb e0 7b db 8d 0f 84 78 02 00 00 e8 dd a5 8d f9 48 8d 7b 78 48 89 f8 48 c1 e8 03 <42> 80 3c 38 00 0f 85 ee 05 00 00 48 8b 04 24 48 8b 6b 78 80 38 00
RSP: 0018:ffff8882066a7bc0 EFLAGS: 00010206
RAX: 000000000000000f RBX: 0000000000000000 RCX: ffffffff87d4ef3a
RDX: 0000000000000000 RSI: ffffffff87d4ece3 RDI: 0000000000000078
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff8880af0c24b0
R13: ffff8880b2e00d80 R14: ffff888052cfd480 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bc4fe0d8e0 CR3: 000000008f44b000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
batadv_iv_ogm_schedule net/batman-adv/bat_iv_ogm.c:1052 [inline]
batadv_iv_ogm_schedule net/batman-adv/bat_iv_ogm.c:1045 [inline]
batadv_iv_send_outstanding_bat_ogm_packet+0x68c/0x7a0 net/batman-adv/bat_iv_ogm.c:1871
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
Modules linked in:
---[ end trace 27611a17ec8ae349 ]---
RIP: 0010:batadv_iv_ogm_schedule_buff+0xc7e/0x1340 net/batman-adv/bat_iv_ogm.c:1026
Code: 80 3c 38 00 0f 85 be 06 00 00 48 8b 1b 48 81 fb e0 7b db 8d 0f 84 78 02 00 00 e8 dd a5 8d f9 48 8d 7b 78 48 89 f8 48 c1 e8 03 <42> 80 3c 38 00 0f 85 ee 05 00 00 48 8b 04 24 48 8b 6b 78 80 38 00
kasan: CONFIG_KASAN_INLINE enabled
RSP: 0018:ffff8882066a7bc0 EFLAGS: 00010206
kasan: GPF could be caused by NULL-ptr deref or user memory access
BTRFS error (device loop1): superblock checksum mismatch
RAX: 000000000000000f RBX: 0000000000000000 RCX: ffffffff87d4ef3a
BTRFS error (device loop1): open_ctree failed
general protection fault: 0000 [#2] PREEMPT SMP KASAN
CPU: 0 PID: 21042 Comm: syz-executor.5 Tainted: G D 4.19.206-syzkaller #0
RDX: 0000000000000000 RSI: ffffffff87d4ece3 RDI: 0000000000000078
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:batadv_hardif_get_by_netdev+0x147/0x3e0 net/batman-adv/hard-interface.c:83
Code: 80 3c 18 00 0f 85 7b 02 00 00 4d 8b 3f 49 81 ff e0 7b db 8d 0f 84 af 01 00 00 e8 74 f5 8a f9 49 8d 7f 20 48 89 f8 48 c1 e8 03 <80> 3c 18 00 0f 85 5e 02 00 00 49 39 6f 20 75 ba e8 54 f5 8a f9 4d
RSP: 0018:ffff8882146feba8 EFLAGS: 00010202
RAX: 0000000000000004 RBX: dffffc0000000000 RCX: ffffc900106af000
RDX: 0000000000040000 RSI: ffffffff87d79d4c RDI: 0000000000000020
RBP: ffff88822ac9c080 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 00000000afc65f54 R12: ffff88822ac9c080
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
FS: 00007f098b6d0700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bc4fe04988 CR3: 000000022b94b000 CR4: 00000000001406f0
R10: 0000000000000001 R11: 0000000000000000 R12: ffff8880af0c24b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
batadv_hard_if_event+0xaf/0x15c0 net/batman-adv/hard-interface.c:1035
R13: ffff8880b2e00d80 R14: ffff888052cfd480 R15: dffffc0000000000
notifier_call_chain+0xc0/0x230 kernel/notifier.c:93
call_netdevice_notifiers net/core/dev.c:1762 [inline]
register_netdevice+0x841/0x10f0 net/core/dev.c:8725
veth_newlink+0x3eb/0x930 drivers/net/veth.c:1142
rtnl_newlink+0x1030/0x15c0 net/core/rtnetlink.c:3141
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f660e02e028 CR3: 00000000a0fe1000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 80 3c 38 00 cmpb $0x0,(%rax,%rdi,1)
4: 0f 85 be 06 00 00 jne 0x6c8
a: 48 8b 1b mov (%rbx),%rbx
d: 48 81 fb e0 7b db 8d cmp $0xffffffff8ddb7be0,%rbx
14: 0f 84 78 02 00 00 je 0x292
1a: e8 dd a5 8d f9 callq 0xf98da5fc
1f: 48 8d 7b 78 lea 0x78(%rbx),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction
2f: 0f 85 ee 05 00 00 jne 0x623
35: 48 8b 04 24 mov (%rsp),%rax
39: 48 8b 6b 78 mov 0x78(%rbx),%rbp
3d: 80 38 00 cmpb $0x0,(%rax)


---
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,
Feb 22, 2022, 10:02:16 PM2/22/22
to syzkaller...@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