[<prev] [next>] [day] [month] [year] [list]
Message-ID: <afbc1c26-8aea-e0b7-47e0-bee0d195a21b@gmail.com>
Date: Sat, 12 Mar 2022 13:36:15 +0300
From: Pavel Skripkin <paskripkin@...il.com>
To: Hillf Danton <hdanton@...a.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Alan Stern <stern@...land.harvard.edu>,
syzbot <syzbot+abd2e0dafb481b621869@...kaller.appspotmail.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] INFO: task hung in port100_probe
Hi Hillf,
On 3/12/22 03:56, Hillf Danton wrote:
>> upstream branch already has my patch: see commit
>> f80cfe2f26581f188429c12bd937eb905ad3ac7b.
>>
> Thanks for your fix.
>
>> let's test previous commit to see if my really fixes this issue
>>
>> #syz test:
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> 3bf7edc84a9eb4007dd9a0cb8878a7e1d5ec6a3b3bf7edc84a9eb4007dd9a0cb8878a7e1d5ec6a3b
>
> Given the Reported-and-tested-by tag in syzbot's echo [1], can you try and
> bisect the curing commit in your spare cycles?
>
> Hillf
>
> [1] https://lore.kernel.org/lkml/00000000000002e20d05d9f663c6@google.com/
>
Hm, that's odd. Last hit was 4d09h ago and I don't see related patches
went it expect for mine.
Will try to bisect...
Also there is a chance, that reproducer is just unstable.
With regards,
Pavel Skripkin
Powered by blists - more mailing lists