All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5ce571007a695806e949@syzkaller.appspotmail.com>
To: glider@google.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in hfs_brec_find
Date: Mon, 06 Feb 2023 04:05:48 -0800	[thread overview]
Message-ID: <000000000000062d6005f406daa8@google.com> (raw)
In-Reply-To: <00000000000043c9a105ef4cccf7@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    eda666ff2276 kmsan: silence -Wmissing-prototypes warnings
git tree:       https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=17bbb96b480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f27365aeb365b358
dashboard link: https://syzkaller.appspot.com/bug?extid=5ce571007a695806e949
compiler:       clang version 15.0.0 (https://github.com/llvm/llvm-project.git 610139d2d9ce6746b3c617fb3e2f7886272d26ff), GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15ac6175480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15e00d23480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fc16035efde4/disk-eda666ff.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/084efc06a321/vmlinux-eda666ff.xz
kernel image: https://storage.googleapis.com/syzbot-assets/35c07fcfcbf2/bzImage-eda666ff.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0f9e3b43e8ac/mount_0.gz

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

WARNING: The mand mount option has been deprecated and
         and is ignored by this kernel. Remove the mand
         option from the mount to silence this warning.
=======================================================
hfs: keylen 9474 too large
=====================================================
BUG: KMSAN: uninit-value in hfs_brec_find+0x671/0x9b0 fs/hfs/bfind.c:141
 hfs_brec_find+0x671/0x9b0 fs/hfs/bfind.c:141
 hfs_brec_read+0x3b/0x190 fs/hfs/bfind.c:165
 hfs_cat_find_brec+0xfb/0x450 fs/hfs/catalog.c:194
 hfs_fill_super+0x1f49/0x2400 fs/hfs/super.c:419
 mount_bdev+0x508/0x840 fs/super.c:1359
 hfs_mount+0x49/0x60 fs/hfs/super.c:456
 legacy_get_tree+0x10c/0x280 fs/fs_context.c:610
 vfs_get_tree+0xa1/0x500 fs/super.c:1489
 do_new_mount+0x694/0x1580 fs/namespace.c:3145
 path_mount+0x71a/0x1eb0 fs/namespace.c:3475
 do_mount fs/namespace.c:3488 [inline]
 __do_sys_mount fs/namespace.c:3697 [inline]
 __se_sys_mount+0x734/0x840 fs/namespace.c:3674
 __ia32_sys_mount+0xdf/0x140 fs/namespace.c:3674
 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
 __do_fast_syscall_32+0xa2/0x100 arch/x86/entry/common.c:178
 do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203
 do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:246
 entry_SYSENTER_compat_after_hwframe+0x70/0x82

Local variable fd created at:
 hfs_fill_super+0x5e/0x2400 fs/hfs/super.c:381
 mount_bdev+0x508/0x840 fs/super.c:1359

CPU: 0 PID: 4991 Comm: syz-executor151 Not tainted 6.2.0-rc6-syzkaller-80422-geda666ff2276 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
=====================================================


  reply	other threads:[~2023-02-06 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  8:26 [syzbot] KMSAN: uninit-value in hfs_brec_find syzbot
2023-02-06 12:05 ` syzbot [this message]
2023-11-02 20:37 ` syzbot
     [not found] <b0a20256-be00-48cf-8ec3-981c3085a80d@app.fastmail.com>
2023-11-02 21:01 ` [syzbot] [hfs?] " 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=000000000000062d6005f406daa8@google.com \
    --to=syzbot+5ce571007a695806e949@syzkaller.appspotmail.com \
    --cc=glider@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.