From: syzbot <syzbot+c1e04a422bbc0f0f2921@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, eddyz87@gmail.com,
haoluo@google.com, hawk@kernel.org, john.fastabend@gmail.com,
jolsa@kernel.org, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
netdev@vger.kernel.org, sdf@fomichev.me, song@kernel.org,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: [syzbot] [bpf?] [net?] stack segment fault in dev_hash_map_redirect
Date: Mon, 01 Jul 2024 15:06:18 -0700 [thread overview]
Message-ID: <00000000000079d168061c36ce83@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 74564adfd352 Add linux-next specific files for 20240701
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=163a0f1e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=111e4e0e6fbde8f0
dashboard link: https://syzkaller.appspot.com/bug?extid=c1e04a422bbc0f0f2921
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/04b8d7db78fb/disk-74564adf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d996f4370003/vmlinux-74564adf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6e7e630054e7/bzImage-74564adf.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c1e04a422bbc0f0f2921@syzkaller.appspotmail.com
Oops: stack segment: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 12368 Comm: syz.0.2084 Not tainted 6.10.0-rc6-next-20240701-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:bpf_net_ctx_get_ri include/linux/filter.h:788 [inline]
RIP: 0010:__bpf_xdp_redirect_map include/linux/filter.h:1672 [inline]
RIP: 0010:dev_hash_map_redirect+0x64/0x620 kernel/bpf/devmap.c:1027
Code: 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 0f 9c 3d 00 48 8b 03 48 89 44 24 08 48 8d 58 38 48 89 dd 48 c1 ed 03 <42> 0f b6 44 3d 00 84 c0 0f 85 f5 03 00 00 44 8b 33 44 89 f6 83 e6
RSP: 0018:ffffc900108f7958 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000038 RCX: 0000000000040000
RDX: ffffc90009834000 RSI: 00000000000001b9 RDI: 00000000000001ba
RBP: 0000000000000007 R08: 0000000000000007 R09: ffffffff81b5e80f
R10: 0000000000000004 R11: ffff888068e5da00 R12: 0000000000000008
R13: 00000000108f79b0 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007fb7f29dc6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000078d4a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
bpf_prog_ec9efaa32d58ce69+0x56/0x5a
__bpf_prog_run include/linux/filter.h:691 [inline]
bpf_prog_run_xdp include/net/xdp.h:514 [inline]
tun_build_skb drivers/net/tun.c:1711 [inline]
tun_get_user+0x3321/0x4560 drivers/net/tun.c:1819
tun_chr_write_iter+0x113/0x1f0 drivers/net/tun.c:2048
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0xa72/0xc90 fs/read_write.c:590
ksys_write+0x1a0/0x2c0 fs/read_write.c:643
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb7f1b7471f
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 29 8c 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 7c 8c 02 00 48
RSP: 002b:00007fb7f29dc010 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fb7f1d03fa0 RCX: 00007fb7f1b7471f
RDX: 000000000000003a RSI: 0000000020000000 RDI: 00000000000000c8
RBP: 00007fb7f1bf677e R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000003a R11: 0000000000000293 R12: 0000000000000000
R13: 000000000000000b R14: 00007fb7f1d03fa0 R15: 00007ffc3bd4c628
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:bpf_net_ctx_get_ri include/linux/filter.h:788 [inline]
RIP: 0010:__bpf_xdp_redirect_map include/linux/filter.h:1672 [inline]
RIP: 0010:dev_hash_map_redirect+0x64/0x620 kernel/bpf/devmap.c:1027
Code: 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 0f 9c 3d 00 48 8b 03 48 89 44 24 08 48 8d 58 38 48 89 dd 48 c1 ed 03 <42> 0f b6 44 3d 00 84 c0 0f 85 f5 03 00 00 44 8b 33 44 89 f6 83 e6
RSP: 0018:ffffc900108f7958 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000038 RCX: 0000000000040000
RDX: ffffc90009834000 RSI: 00000000000001b9 RDI: 00000000000001ba
RBP: 0000000000000007 R08: 0000000000000007 R09: ffffffff81b5e80f
R10: 0000000000000004 R11: ffff888068e5da00 R12: 0000000000000008
R13: 00000000108f79b0 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007fb7f29dc6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000078d4a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 00 48 89 add %cl,-0x77(%rax)
3: d8 48 c1 fmuls -0x3f(%rax)
6: e8 03 42 80 3c call 0x3c80420e
b: 38 00 cmp %al,(%rax)
d: 74 08 je 0x17
f: 48 89 df mov %rbx,%rdi
12: e8 0f 9c 3d 00 call 0x3d9c26
17: 48 8b 03 mov (%rbx),%rax
1a: 48 89 44 24 08 mov %rax,0x8(%rsp)
1f: 48 8d 58 38 lea 0x38(%rax),%rbx
23: 48 89 dd mov %rbx,%rbp
26: 48 c1 ed 03 shr $0x3,%rbp
* 2a: 42 0f b6 44 3d 00 movzbl 0x0(%rbp,%r15,1),%eax <-- trapping instruction
30: 84 c0 test %al,%al
32: 0f 85 f5 03 00 00 jne 0x42d
38: 44 8b 33 mov (%rbx),%r14d
3b: 44 89 f6 mov %r14d,%esi
3e: 83 .byte 0x83
3f: e6 .byte 0xe6
---
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
next reply other threads:[~2024-07-01 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 22:06 syzbot [this message]
2024-07-06 5:08 ` [syzbot] [bpf?] [net?] stack segment fault in dev_hash_map_redirect syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000079d168061c36ce83@google.com \
--to=syzbot+c1e04a422bbc0f0f2921@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).