From: Martin KaFai Lau <martin.lau@linux.dev>
To: syzbot <syzbot+5e23b0df3b12b8b215b7@syzkaller.appspotmail.com>
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, 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 percpu_array_map_lookup_elem
Date: Mon, 8 Apr 2024 22:37:21 -0700 [thread overview]
Message-ID: <fb458efd-0bc9-4a9d-aff1-e979b7abc710@linux.dev> (raw)
In-Reply-To: <0000000000004139c80614076a2c@google.com>
On 3/19/24 11:12 AM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: e5eb28f6d1af Merge tag 'mm-nonmm-stable-2024-03-14-09-36' ..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=14e351c9180000
> kernel config: https://syzkaller.appspot.com/x/.config?x=aa3d79b689f321c8
> dashboard link: https://syzkaller.appspot.com/bug?extid=5e23b0df3b12b8b215b7
> 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=14498006180000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11e4d769180000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/eaca555a0446/disk-e5eb28f6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/4fbf90fa0d23/vmlinux-e5eb28f6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/bbae0627aafd/bzImage-e5eb28f6.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+5e23b0df3b12b8b215b7@syzkaller.appspotmail.com
>
> =====================================================
> BUG: KMSAN: uninit-value in percpu_array_map_lookup_elem+0x142/0x160 kernel/bpf/arraymap.c:243
> percpu_array_map_lookup_elem+0x142/0x160 kernel/bpf/arraymap.c:243
> ____bpf_map_lookup_elem kernel/bpf/helpers.c:42 [inline]
> bpf_map_lookup_elem+0x5c/0x80 kernel/bpf/helpers.c:38
> ___bpf_prog_run+0x13fe/0xe0f0 kernel/bpf/core.c:1997
> __bpf_prog_run64+0xb5/0xe0 kernel/bpf/core.c:2236
#syz dup: [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_lookup_elem
> bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline]
> __bpf_prog_run include/linux/filter.h:657 [inline]
> bpf_prog_run include/linux/filter.h:664 [inline]
> __bpf_trace_run kernel/trace/bpf_trace.c:2381 [inline]
> bpf_trace_run3+0x132/0x320 kernel/trace/bpf_trace.c:2421
> __bpf_trace_ext4_es_insert_delayed_block+0x34/0x50 include/trace/events/ext4.h:2481
> trace_ext4_es_insert_delayed_block include/trace/events/ext4.h:2481 [inline]
> ext4_es_insert_delayed_block+0x11e1/0x1290 fs/ext4/extents_status.c:2082
> ext4_insert_delayed_block fs/ext4/inode.c:1676 [inline]
> ext4_da_map_blocks fs/ext4/inode.c:1777 [inline]
> ext4_da_get_block_prep+0x1714/0x1d30 fs/ext4/inode.c:1817
> ext4_block_write_begin+0x749/0x1df0 fs/ext4/inode.c:1055
> ext4_da_write_begin+0x889/0xec0 fs/ext4/inode.c:2894
> generic_perform_write+0x400/0xc60 mm/filemap.c:3974
> ext4_buffered_write_iter+0x564/0xaa0 fs/ext4/file.c:299
> ext4_file_write_iter+0x208/0x3450
> call_write_iter include/linux/fs.h:2108 [inline]
> new_sync_write fs/read_write.c:497 [inline]
> vfs_write+0xb63/0x1520 fs/read_write.c:590
> ksys_write+0x20f/0x4c0 fs/read_write.c:643
> __do_sys_write fs/read_write.c:655 [inline]
> __se_sys_write fs/read_write.c:652 [inline]
> __x64_sys_write+0x93/0xe0 fs/read_write.c:652
> do_syscall_64+0xd5/0x1f0
> entry_SYSCALL_64_after_hwframe+0x6d/0x75
>
> Local variable stack created at:
> __bpf_prog_run64+0x45/0xe0 kernel/bpf/core.c:2236
> bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline]
> __bpf_prog_run include/linux/filter.h:657 [inline]
> bpf_prog_run include/linux/filter.h:664 [inline]
> __bpf_trace_run kernel/trace/bpf_trace.c:2381 [inline]
> bpf_trace_run3+0x132/0x320 kernel/trace/bpf_trace.c:2421
>
> CPU: 1 PID: 5001 Comm: syz-executor118 Not tainted 6.8.0-syzkaller-09791-ge5eb28f6d1af #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
> =====================================================
prev parent reply other threads:[~2024-04-09 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 18:12 [syzbot] [bpf?] KMSAN: uninit-value in percpu_array_map_lookup_elem syzbot
2024-04-09 5:37 ` Martin KaFai Lau [this message]
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=fb458efd-0bc9-4a9d-aff1-e979b7abc710@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=eddyz87@gmail.com \
--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+5e23b0df3b12b8b215b7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox