Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <9f4287ae-21f6-5c2a-fed7-6cc7606c7e8c@gmail.com>
Date:   Sat, 12 Mar 2022 15:44:58 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.1
Subject: Re: [syzbot] INFO: task hung in port100_probe
Content-Language: en-US
To:     Hillf Danton <hdanton@sina.com>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
        Alan Stern <stern@rowland.harvard.edu>,
        syzbot <syzbot+abd2e0dafb481b621869@syzkaller.appspotmail.com>,
        linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
        syzkaller-bugs@googlegroups.com
References: <20220310084247.1148-1-hdanton@sina.com>
 <20220311053751.1226-1-hdanton@sina.com>
 <20220312005624.1310-1-hdanton@sina.com>
 <20220312115854.1399-1-hdanton@sina.com>
From:   Pavel Skripkin <paskripkin@gmail.com>
In-Reply-To: <20220312115854.1399-1-hdanton@sina.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Hillf,

On 3/12/22 14:58, Hillf Danton wrote:
> On Sat, 12 Mar 2022 13:36:15 +0300 Pavel Skripkin  wrote:
>> 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 
> 
> Wonder if you mean it was reproduced four days ago by "Last hit was 4d09h ago".

Yes, exactly.

> If it was then can you share the splat? Anything different from the
> syzbot report [2] on Tue, 22 Jun 2021?
> 

IIRC syzbot tests on top of newest updates. I.e. last time syzbot 
reproduced this issue on top of v5.17-rc7 at least. So fix commit should 
somewhere between v5.17-rc7..HEAD


With regards,
Pavel Skripkin