From: Pavel Skripkin <paskripkin@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: syzbot <syzbot+f44badb06036334e867a@syzkaller.appspotmail.com>,
davem@davemloft.net, glider@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux@rempel-privat.de, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KMSAN: uninit-value in asix_mdio_read (2)
Date: Sun, 19 Dec 2021 01:01:34 +0300 [thread overview]
Message-ID: <4a4b7a7c-5f88-b30d-360b-d6d70e7fc69f@gmail.com> (raw)
In-Reply-To: <Yb5Vu8+45wh5FiCQ@lunn.ch>
On 12/19/21 00:42, Andrew Lunn wrote:
> On Sun, Dec 19, 2021 at 12:14:30AM +0300, Pavel Skripkin wrote:
>> On 12/18/21 14:07, syzbot wrote:
>> > Hello,
>> >
>> > syzbot found the following issue on:
>> >
>> > HEAD commit: b0a8b5053e8b kmsan: core: add dependency on DEBUG_KERNEL
>> > git tree: https://github.com/google/kmsan.git master
>> > console output: https://syzkaller.appspot.com/x/log.txt?x=13a4d133b00000
>> > kernel config: https://syzkaller.appspot.com/x/.config?x=46a956fc7a887c60
>> > dashboard link: https://syzkaller.appspot.com/bug?extid=f44badb06036334e867a
>> > compiler: clang version 14.0.0 (/usr/local/google/src/llvm-git-monorepo 2b554920f11c8b763cd9ed9003f4e19b919b8e1f), GNU ld (GNU Binutils for Debian) 2.35.2
>> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149fddcbb00000
>> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17baef25b00000
>> >
>> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> > Reported-by: syzbot+f44badb06036334e867a@syzkaller.appspotmail.com
>> >
>>
>> The last unhanded case is asix_read_cmd() == 0. Let's handle it...
>
> That does not look correct, i think.
>
> asix_read_cmd() == 0 means no error from the read itself. If there is
> no error, we should look at the value of smsr and test for bit
As far as I understand asix_read_cmd() == 0 means 0 bytes was read,
since it just returns usb_control_msg() return value. I don't know if
usb_control_msg() can ever return 0, but looks like it's the only
unhanded case
> AX_HOST_EN. Doing a continue means we just ignore the value returned
> by the good read.
>
> I think the correct fix is to look at the value of i. If we have
> exceeded 30, we should return -ETIMEDOUT.
>
Sorry, I don't get how it can help. Report says, that on following line
else if (smsr & AX_HOST_EN)
smsr is uninitialized. How value of i can help here?
Can you, please, explain if you don't mind :)
Thanks
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2021-12-18 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 11:07 [syzbot] KMSAN: uninit-value in asix_mdio_read (2) syzbot
2021-12-18 21:14 ` Pavel Skripkin
2021-12-18 21:42 ` Andrew Lunn
2021-12-18 22:01 ` Pavel Skripkin [this message]
2021-12-19 1:03 ` syzbot
2021-12-19 17:17 ` Andrew Lunn
2021-12-19 21:15 ` Pavel Skripkin
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=4a4b7a7c-5f88-b30d-360b-d6d70e7fc69f@gmail.com \
--to=paskripkin@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=glider@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=netdev@vger.kernel.org \
--cc=syzbot+f44badb06036334e867a@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