From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+91f02b28f9bb5f5f1341@syzkaller.appspotmail.com>
Cc: glider@google.com, jack@suse.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KMSAN: uninit-value in udf_evict_inode
Date: Fri, 25 Sep 2020 12:33:15 +0200 [thread overview]
Message-ID: <20200925103315.GD11772@quack2.suse.cz> (raw)
In-Reply-To: <000000000000f6599a05b01c71ed@google.com>
On Thu 24-09-20 22:18:21, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: c5a13b33 kmsan: clang-format core
> git tree: https://github.com/google/kmsan.git master
> console output: https://syzkaller.appspot.com/x/log.txt?x=142cf809900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=20f149ad694ba4be
> dashboard link: https://syzkaller.appspot.com/bug?extid=91f02b28f9bb5f5f1341
> compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> userspace arch: i386
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+91f02b28f9bb5f5f1341@syzkaller.appspotmail.com
>
> UDF-fs: warning (device loop3): udf_load_vrs: No anchor found
> UDF-fs: Scanning with blocksize 512 failed
> UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2020/09/19 18:44 (1000)
> UDF-fs: error (device loop3): udf_read_inode: (ino 1328) failed !bh
> =====================================================
> BUG: KMSAN: uninit-value in udf_evict_inode+0x382/0x7d0 fs/udf/inode.c:150
Yeah, easy enough. I'll send a fix.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-09-25 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 5:18 syzbot
2020-09-25 10:33 ` Jan Kara [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=20200925103315.GD11772@quack2.suse.cz \
--to=jack@suse.cz \
--cc=glider@google.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+91f02b28f9bb5f5f1341@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®