[v6.1] WARNING in __xdp_reg_mem_model

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cd5d98c0556c Linux 6.1.86
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12870e3b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1002eed7bd96ee12
dashboard link: https://syzkaller.appspot.com/bug?extid=d93a626e7fffa5547e57
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1497cbd9943e/disk-cd5d98c0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9f947b67d7b1/vmlinux-cd5d98c0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92c97ada9d02/bzImage-cd5d98c0.xz

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

RBP: 00007febbb167120 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 000000000000000b R14: 00007febba5abf80 R15: 00007fff732cb048
</TASK>
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3925 at net/core/xdp.c:296 __xdp_reg_mem_model+0x2d5/0x620 net/core/xdp.c:294
Modules linked in:
CPU: 0 PID: 3925 Comm: syz-executor.3 Not tainted 6.1.86-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__xdp_reg_mem_model+0x2d5/0x620 net/core/xdp.c:296
Code: 41 89 c5 85 c0 79 5b e8 39 dd fa f8 eb a5 e8 32 dd fa f8 4c 89 ff e8 ba d9 37 f9 4d 63 e4 48 c7 c7 c0 59 2a 8e e8 1b a2 03 02 <0f> 0b e9 e3 01 00 00 e8 0f dd fa f8 48 8d 7c 24 60 48 89 f8 48 c1
RSP: 0018:ffffc9000a92f680 EFLAGS: 00010246
RAX: f2369657b6c4ef00 RBX: 1ffff92001525ed8 RCX: ffffffff8a935678
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffc9000a92f600
RBP: ffffc9000a92f750 R08: dffffc0000000000 R09: fffff52001525ec1
R10: 0000000000000000 R11: dffffc0000000001 R12: fffffffffffffff4
R13: dffffc0000000000 R14: 0000000000000002 R15: ffffc9000a92f9a0
FS: 00007febbb1676c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000100000000 CR3: 000000007dba7000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
xdp_reg_mem_model+0x1e/0x30 net/core/xdp.c:341
xdp_test_run_setup net/bpf/test_run.c:177 [inline]
bpf_test_run_xdp_live+0x365/0x1ea0 net/bpf/test_run.c:355
bpf_prog_test_run_xdp+0x7d1/0x1130 net/bpf/test_run.c:1387
bpf_prog_test_run+0x32f/0x3a0 kernel/bpf/syscall.c:3670
__sys_bpf+0x3eb/0x6c0 kernel/bpf/syscall.c:5023
__do_sys_bpf kernel/bpf/syscall.c:5109 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5107 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:5107
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7febba47dea9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007febbb1670c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007febba5abf80 RCX: 00007febba47dea9
RDX: 0000000000000050 RSI: 0000000020000340 RDI: 000000000000000a
RBP: 00007febbb167120 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 000000000000000b R14: 00007febba5abf80 R15: 00007fff732cb048
</TASK>


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

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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: cd5d98c0556c Linux 6.1.86
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=16b4b8f7180000

kernel config: https://syzkaller.appspot.com/x/.config?x=1002eed7bd96ee12
dashboard link: https://syzkaller.appspot.com/bug?extid=d93a626e7fffa5547e57
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127aba3b180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1781d557180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1497cbd9943e/disk-cd5d98c0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9f947b67d7b1/vmlinux-cd5d98c0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92c97ada9d02/bzImage-cd5d98c0.xz

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

RDX: 0000000000000050 RSI: 0000000020000340 RDI: 000000000000000a

RBP: 0000000000000001 R08: 00007ffea6550ea7 R09: 00000000000000a0
R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001

</TASK>
------------[ cut here ]------------

WARNING: CPU: 0 PID: 3543 at net/core/xdp.c:296 __xdp_reg_mem_model+0x2d5/0x620 net/core/xdp.c:294
Modules linked in:
CPU: 0 PID: 3543 Comm: syz-executor846 Not tainted 6.1.86-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__xdp_reg_mem_model+0x2d5/0x620 net/core/xdp.c:296
Code: 41 89 c5 85 c0 79 5b e8 39 dd fa f8 eb a5 e8 32 dd fa f8 4c 89 ff e8 ba d9 37 f9 4d 63 e4 48 c7 c7 c0 59 2a 8e e8 1b a2 03 02 <0f> 0b e9 e3 01 00 00 e8 0f dd fa f8 48 8d 7c 24 60 48 89 f8 48 c1

RSP: 0018:ffffc900039df680 EFLAGS: 00010246
RAX: 58241fc6aa612700 RBX: 1ffff9200073bed8 RCX: ffffffff8a935678
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffc900039df600
RBP: ffffc900039df750 R08: dffffc0000000000 R09: fffff5200073bec1

R10: 0000000000000000 R11: dffffc0000000001 R12: fffffffffffffff4

R13: dffffc0000000000 R14: 0000000000000002 R15: ffffc900039df9a0
FS: 000055555649f380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f8e6d290020 CR3: 00000000775df000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Call Trace:
<TASK>
xdp_reg_mem_model+0x1e/0x30 net/core/xdp.c:341
xdp_test_run_setup net/bpf/test_run.c:177 [inline]
bpf_test_run_xdp_live+0x365/0x1ea0 net/bpf/test_run.c:355
bpf_prog_test_run_xdp+0x7d1/0x1130 net/bpf/test_run.c:1387
bpf_prog_test_run+0x32f/0x3a0 kernel/bpf/syscall.c:3670
__sys_bpf+0x3eb/0x6c0 kernel/bpf/syscall.c:5023
__do_sys_bpf kernel/bpf/syscall.c:5109 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5107 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:5107
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2

RIP: 0033:0x7f8e6d25d079
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffea6551108 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007ffea6551120 RCX: 00007f8e6d25d079

RDX: 0000000000000050 RSI: 0000000020000340 RDI: 000000000000000a

RBP: 0000000000000001 R08: 00007ffea6550ea7 R09: 00000000000000a0
R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.