From: syzbot <syzbot+24ac24ff58dc5b0d26b9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [squashfs?] KMSAN: uninit-value in pick_link
Date: Thu, 01 Aug 2024 04:44:04 -0700 [thread overview]
Message-ID: <00000000000046def5061e9dba03@google.com> (raw)
In-Reply-To: <20240801092733.1243313-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in pick_link
loop0: detected capacity change from 0 to 8
err: 0, folio: ffffea00057726d0, in: ffff888121ab45b8, do_read_cache_folio
=====================================================
BUG: KMSAN: uninit-value in pick_link+0xd8c/0x1690 fs/namei.c:1850
pick_link+0xd8c/0x1690 fs/namei.c:1850
step_into+0x156f/0x1640 fs/namei.c:1909
open_last_lookups fs/namei.c:3674 [inline]
path_openat+0x39da/0x6100 fs/namei.c:3883
do_filp_open+0x20e/0x590 fs/namei.c:3913
do_sys_openat2+0x1bf/0x2f0 fs/open.c:1416
do_sys_open fs/open.c:1431 [inline]
__do_sys_openat fs/open.c:1447 [inline]
__se_sys_openat fs/open.c:1442 [inline]
__x64_sys_openat+0x2a1/0x310 fs/open.c:1442
x64_sys_call+0x1fe/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:258
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was created at:
__alloc_pages_noprof+0x9d6/0xe70 mm/page_alloc.c:4719
alloc_pages_mpol_noprof+0x299/0x990 mm/mempolicy.c:2263
alloc_pages_noprof mm/mempolicy.c:2343 [inline]
folio_alloc_noprof+0x1db/0x310 mm/mempolicy.c:2350
filemap_alloc_folio_noprof+0xa6/0x440 mm/filemap.c:1008
do_read_cache_folio+0x134/0x1300 mm/filemap.c:3753
do_read_cache_page mm/filemap.c:3860 [inline]
read_cache_page+0x63/0x1d0 mm/filemap.c:3869
read_mapping_page include/linux/pagemap.h:907 [inline]
page_get_link+0x76/0xf90 fs/namei.c:5272
pick_link+0xd6c/0x1690
step_into+0x156f/0x1640 fs/namei.c:1909
open_last_lookups fs/namei.c:3674 [inline]
path_openat+0x39da/0x6100 fs/namei.c:3883
do_filp_open+0x20e/0x590 fs/namei.c:3913
do_sys_openat2+0x1bf/0x2f0 fs/open.c:1416
do_sys_open fs/open.c:1431 [inline]
__do_sys_openat fs/open.c:1447 [inline]
__se_sys_openat fs/open.c:1442 [inline]
__x64_sys_openat+0x2a1/0x310 fs/open.c:1442
x64_sys_call+0x1fe/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:258
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 UID: 0 PID: 5981 Comm: syz.0.15 Not tainted 6.10.0-syzkaller-12708-g2f8c4f506285-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
=====================================================
Tested on:
commit: 2f8c4f50 Merge tag 'auxdisplay-for-v6.11-tag1' of git:..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=169f9b03980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea3a063e5f96c3d6
dashboard link: https://syzkaller.appspot.com/bug?extid=24ac24ff58dc5b0d26b9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=14cdd19d980000
next parent reply other threads:[~2024-08-01 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240801092733.1243313-1-lizhi.xu@windriver.com>
2024-08-01 11:44 ` syzbot [this message]
[not found] <20240803031347.1275196-1-lizhi.xu@windriver.com>
2024-08-03 4:09 ` [syzbot] [squashfs?] KMSAN: uninit-value in pick_link syzbot
[not found] <20240803030358.1213065-1-lizhi.xu@windriver.com>
2024-08-03 3:41 ` syzbot
[not found] <20240802020037.976956-1-lizhi.xu@windriver.com>
2024-08-02 2:29 ` syzbot
[not found] <20240802010252.214842-1-lizhi.xu@windriver.com>
2024-08-02 1:33 ` syzbot
[not found] <20240801143944.78059-1-lizhi.xu@windriver.com>
2024-08-01 15:11 ` syzbot
[not found] <20240801140831.4016416-1-lizhi.xu@windriver.com>
2024-08-01 14:32 ` syzbot
[not found] <20240801130611.3460940-1-lizhi.xu@windriver.com>
2024-08-01 13:38 ` syzbot
[not found] <20240801120853.2962357-1-lizhi.xu@windriver.com>
2024-08-01 12:42 ` syzbot
[not found] <20240801090658.1894596-1-lizhi.xu@windriver.com>
2024-08-01 11:21 ` syzbot
[not found] <20240801012343.412607-1-lizhi.xu@windriver.com>
2024-08-01 1:55 ` syzbot
2024-07-31 8:12 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=00000000000046def5061e9dba03@google.com \
--to=syzbot+24ac24ff58dc5b0d26b9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=syzkaller-bugs@googlegroups.com \
/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