From: Martin KaFai Lau <martin.lau@linux.dev>
To: syzbot <syzbot+c2dc95f7d0825a145992@syzkaller.appspotmail.com>
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, sdf@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] KMSAN: uninit-value in bpf_bprintf_prepare
Date: Mon, 8 Apr 2024 22:35:12 -0700 [thread overview]
Message-ID: <b85ed24e-e7ed-49b8-b93a-cb0f9e32540c@linux.dev> (raw)
In-Reply-To: <000000000000a1a6990611ea8b4d@google.com>
On 2/21/24 12:55 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: c1ca10ceffbb Merge tag 'scsi-fixes' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1364db0c180000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e3dd779fba027968
> dashboard link: https://syzkaller.appspot.com/bug?extid=c2dc95f7d0825a145992
> 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/83d019f0ac47/disk-c1ca10ce.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/49e05dd7a23d/vmlinux-c1ca10ce.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/68ec9fa2d33d/bzImage-c1ca10ce.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+c2dc95f7d0825a145992@syzkaller.appspotmail.com
>
> =====================================================
> BUG: KMSAN: uninit-value in bpf_bprintf_prepare+0x20d7/0x23b0 kernel/bpf/helpers.c:904
> bpf_bprintf_prepare+0x20d7/0x23b0 kernel/bpf/helpers.c:904
> ____bpf_snprintf kernel/bpf/helpers.c:1060 [inline]
> bpf_snprintf+0x141/0x360 kernel/bpf/helpers.c:1044
> ___bpf_prog_run+0x2180/0xdb80 kernel/bpf/core.c:1986
> __bpf_prog_run288+0xb5/0xe0 kernel/bpf/core.c:2226
#syz dup: [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_lookup_elem
> bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline]
> __bpf_prog_run include/linux/filter.h:651 [inline]
> bpf_prog_run include/linux/filter.h:658 [inline]
> bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline]
> bpf_flow_dissect+0x127/0x470 net/core/flow_dissector.c:991
> bpf_prog_test_run_flow_dissector+0x6f4/0xa20 net/bpf/test_run.c:1359
> bpf_prog_test_run+0x6af/0xac0 kernel/bpf/syscall.c:4107
> __sys_bpf+0x649/0xd60 kernel/bpf/syscall.c:5475
> __do_sys_bpf kernel/bpf/syscall.c:5561 [inline]
> __se_sys_bpf kernel/bpf/syscall.c:5559 [inline]
> __x64_sys_bpf+0xa0/0xe0 kernel/bpf/syscall.c:5559
> do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe+0x63/0x6b
>
> Local variable stack created at:
> __bpf_prog_run288+0x45/0xe0 kernel/bpf/core.c:2226
> bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline]
> __bpf_prog_run include/linux/filter.h:651 [inline]
> bpf_prog_run include/linux/filter.h:658 [inline]
> bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline]
> bpf_flow_dissect+0x127/0x470 net/core/flow_dissector.c:991
>
> CPU: 0 PID: 6318 Comm: syz-executor.2 Not tainted 6.8.0-rc4-syzkaller-00331-gc1ca10ceffbb #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
> =====================================================
next prev parent reply other threads:[~2024-04-09 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 20:55 [syzbot] [bpf?] KMSAN: uninit-value in bpf_bprintf_prepare syzbot
2024-03-03 6:48 ` syzbot
2024-04-09 5:35 ` Martin KaFai Lau [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 15:48 xingwei lee
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=b85ed24e-e7ed-49b8-b93a-cb0f9e32540c@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzbot+c2dc95f7d0825a145992@syzkaller.appspotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.