From: syzbot <syzbot+e7d46eb426883fb97efd@syzkaller.appspotmail.com>
To: glider@google.com, gregkh@linuxfoundation.org,
jaskaransingh7654321@gmail.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com,
usb-storage@lists.one-eyed-alien.net
Subject: Re: KMSAN: uninit-value in alauda_check_media
Date: Fri, 11 Oct 2019 08:42:01 -0700 [thread overview]
Message-ID: <000000000000ea5bf90594a45b81@google.com> (raw)
In-Reply-To: <CAG_fn=WsN0d8VO6=4jtDP9rHqBMp0zBvJQ7qrvQhZkkaj6NNsg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
KMSAN: uninit-value in alauda_check_media
=====================================================
BUG: KMSAN: uninit-value in alauda_transport+0x462/0x57f0
drivers/usb/storage/alauda.c:1138
CPU: 1 PID: 11015 Comm: usb-storage Not tainted 5.4.0-rc2+ #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x191/0x1f0 lib/dump_stack.c:113
kmsan_report+0x14c/0x2c0 mm/kmsan/kmsan_report.c:110
__msan_warning+0x73/0xe0 mm/kmsan/kmsan_instr.c:245
alauda_check_media+0x344/0x3310 drivers/usb/storage/alauda.c:461
alauda_transport+0x462/0x57f0 drivers/usb/storage/alauda.c:1138
usb_stor_invoke_transport+0xf5/0x27e0 drivers/usb/storage/transport.c:606
usb_stor_transparent_scsi_command+0x5d/0x70
drivers/usb/storage/protocol.c:108
usb_stor_control_thread+0xca6/0x11a0 drivers/usb/storage/usb.c:380
kthread+0x4b5/0x4f0 kernel/kthread.c:256
ret_from_fork+0x35/0x40 arch/x86/entry/entry_64.S:355
Local variable description: ----status@alauda_check_media
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 11015 Comm: usb-storage Tainted: G B 5.4.0-rc2+
#0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x191/0x1f0 lib/dump_stack.c:113
panic+0x3c9/0xc1e kernel/panic.c:220
kmsan_report+0x2b4/0x2c0 mm/kmsan/kmsan_report.c:133
__msan_warning+0x73/0xe0 mm/kmsan/kmsan_instr.c:245
alauda_check_media+0x344/0x3310 drivers/usb/storage/alauda.c:461
alauda_transport+0x462/0x57f0 drivers/usb/storage/alauda.c:1138
usb_stor_invoke_transport+0xf5/0x27e0 drivers/usb/storage/transport.c:606
usb_stor_transparent_scsi_command+0x5d/0x70
drivers/usb/storage/protocol.c:108
usb_stor_control_thread+0xca6/0x11a0 drivers/usb/storage/usb.c:380
kthread+0x4b5/0x4f0 kernel/kthread.c:256
ret_from_fork+0x35/0x40 arch/x86/entry/entry_64.S:355
Kernel Offset: disabled
Rebooting in 86400 seconds..
Tested on:
commit: c40e5c97 kmsan: drop some dead code in kmsan_shadow.c
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=153ba453600000
kernel config: https://syzkaller.appspot.com/x/.config?x=49548798e87d32d7
dashboard link: https://syzkaller.appspot.com/bug?extid=e7d46eb426883fb97efd
compiler: clang version 9.0.0 (/home/glider/llvm/clang
80fee25776c2fb61e74c1ecb1a523375c2500b69)
next prev parent reply other threads:[~2019-10-11 15:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 19:39 KMSAN: uninit-value in alauda_check_media syzbot
2019-10-11 11:23 ` Jaskaran Singh
2019-10-11 11:51 ` Alexander Potapenko
2019-10-11 15:42 ` syzbot [this message]
2019-10-11 14:08 ` Alan Stern
2019-10-11 14:18 ` Andrey Konovalov
2019-10-11 14:53 ` Alan Stern
2019-10-11 15:06 ` Greg Kroah-Hartman
2019-10-14 12:56 ` Andrey Konovalov
2019-10-11 15:24 ` syzbot
2021-12-28 7:47 ` Christophe JAILLET
2021-12-28 7:47 ` syzbot
2021-12-28 22:49 ` Alan Stern
2021-12-29 9:16 ` Christophe JAILLET
2021-12-29 16:45 ` Alan Stern
2021-12-28 8:01 ` Christophe JAILLET
2021-12-28 11:10 ` [syzbot] " syzbot
-- strict thread matches above, loose matches on Subject: below --
2019-10-11 11:17 Jas K
[not found] <cca3b7b4-d9cf-a275-ec0a-c99720a94049@wanadoo.fr>
2021-12-28 7:52 ` syzbot
2023-08-02 16:05 Alan Stern
2023-08-02 16:05 ` syzbot
2023-08-02 16:35 ` Alan Stern
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=000000000000ea5bf90594a45b81@google.com \
--to=syzbot+e7d46eb426883fb97efd@syzkaller.appspotmail.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaskaransingh7654321@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=usb-storage@lists.one-eyed-alien.net \
/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.