[syzbot] [net?] BUG: unable to handle kernel paging request in bond_rr_gen_slave_id (3)

[syzbot <syzbot+80e046b8da2820b6ba73@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    2061f18ad76e Merge tag 'caps-pr-20251204' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15a27192580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c3dd7b11863a05ae
dashboard link: https://syzkaller.appspot.com/bug?extid=80e046b8da2820b6ba73
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-2061f18a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c6a2ca6b83cd/vmlinux-2061f18a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e0719cd80772/bzImage-2061f18a.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+80e046b8da2820b6ba73@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: ffff8880d6b60000
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 1b201067 P4D 1b201067 PUD 0 
Oops: Oops: 0002 [#1] SMP KASAN NOPTI
CPU: 2 UID: 0 PID: 18510 Comm: syz.7.3743 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:bond_rr_gen_slave_id+0x1d5/0x250 drivers/net/bonding/bond_main.c:4836
Code: bc 24 f0 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 7a 49 8b 84 24 f0 00 00 00 bb 01 00 00 00 <65> 0f c1 18 e8 82 f5 73 fb 83 c3 01 89 d8 5b 5d 41 5c 41 5d 41 5e
RSP: 0018:ffffc900039d75d0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffc90034e9f000
RDX: 1ffff1100c6b61ce RSI: ffffffff864a3089 RDI: ffff8880635b0e70
RBP: ffff8880635b0000 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000001 R11: 000000000ac0d5af R12: ffff8880635b0d80
R13: 0000000000008f00 R14: ffff8880635b0d80 R15: dffffc0000000000
FS:  00007f96076d66c0(0000) GS:ffff8880d6b60000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8880d6b60000 CR3: 0000000113c4b000 CR4: 0000000000352ef0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000083
DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 bond_xdp_xmit_roundrobin_slave_get drivers/net/bonding/bond_main.c:4923 [inline]
 bond_xdp_get_xmit_slave+0x2a9/0x6b0 drivers/net/bonding/bond_main.c:5506
 xdp_master_redirect+0x161/0x330 net/core/filter.c:4388
 bpf_prog_run_xdp include/net/xdp.h:700 [inline]
 xdp_test_run_batch.constprop.0+0x14ce/0x1b20 net/bpf/test_run.c:307
 bpf_test_run_xdp_live+0x365/0x770 net/bpf/test_run.c:379
 bpf_prog_test_run_xdp+0xd3d/0x1660 net/bpf/test_run.c:1388
 bpf_prog_test_run kernel/bpf/syscall.c:4703 [inline]
 __sys_bpf+0x1035/0x4980 kernel/bpf/syscall.c:6182
 __do_sys_bpf kernel/bpf/syscall.c:6274 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:6272 [inline]
 __x64_sys_bpf+0x78/0xc0 kernel/bpf/syscall.c:6272
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f960678f7c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f96076d6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f96069e5fa0 RCX: 00007f960678f7c9
RDX: 0000000000000050 RSI: 0000200000000600 RDI: 000000000000000a
RBP: 00007f9606813f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f96069e6038 R14: 00007f96069e5fa0 R15: 00007ffd7a8f7488
 </TASK>
Modules linked in:
CR2: ffff8880d6b60000
---[ end trace 0000000000000000 ]---
RIP: 0010:bond_rr_gen_slave_id+0x1d5/0x250 drivers/net/bonding/bond_main.c:4836
Code: bc 24 f0 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 7a 49 8b 84 24 f0 00 00 00 bb 01 00 00 00 <65> 0f c1 18 e8 82 f5 73 fb 83 c3 01 89 d8 5b 5d 41 5c 41 5d 41 5e
RSP: 0018:ffffc900039d75d0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffc90034e9f000
RDX: 1ffff1100c6b61ce RSI: ffffffff864a3089 RDI: ffff8880635b0e70
RBP: ffff8880635b0000 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000001 R11: 000000000ac0d5af R12: ffff8880635b0d80
R13: 0000000000008f00 R14: ffff8880635b0d80 R15: dffffc0000000000
FS:  00007f96076d66c0(0000) GS:ffff8880d6b60000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8880d6b60000 CR3: 0000000113c4b000 CR4: 0000000000352ef0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000083
DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 4 bytes skipped:
   0:	00 00                	add    %al,(%rax)
   2:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
   9:	fc ff df
   c:	48 89 fa             	mov    %rdi,%rdx
   f:	48 c1 ea 03          	shr    $0x3,%rdx
  13:	80 3c 02 00          	cmpb   $0x0,(%rdx,%rax,1)
  17:	75 7a                	jne    0x93
  19:	49 8b 84 24 f0 00 00 	mov    0xf0(%r12),%rax
  20:	00
  21:	bb 01 00 00 00       	mov    $0x1,%ebx
* 26:	65 0f c1 18          	xadd   %ebx,%gs:(%rax) <-- trapping instruction
  2a:	e8 82 f5 73 fb       	call   0xfb73f5b1
  2f:	83 c3 01             	add    $0x1,%ebx
  32:	89 d8                	mov    %ebx,%eax
  34:	5b                   	pop    %rbx
  35:	5d                   	pop    %rbp
  36:	41 5c                	pop    %r12
  38:	41 5d                	pop    %r13
  3a:	41 5e                	pop    %r14


---
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 syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup