From: Pavel Skripkin <paskripkin@gmail.com>
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
Subject: Re: [syzbot] INFO: task hung in port100_probe
Date: Sat, 12 Mar 2022 13:36:15 +0300 [thread overview]
Message-ID: <afbc1c26-8aea-e0b7-47e0-bee0d195a21b@gmail.com> (raw)
In-Reply-To: <20220312005624.1310-1-hdanton@sina.com>
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
next prev parent reply other threads:[~2022-03-12 10:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220310084247.1148-1-hdanton@sina.com>
2022-03-10 14:22 ` [syzbot] INFO: task hung in port100_probe syzbot
[not found] ` <20220311053751.1226-1-hdanton@sina.com>
2022-03-11 19:17 ` Pavel Skripkin
2022-03-11 19:18 ` syzbot
2022-03-11 19:19 ` Pavel Skripkin
2022-03-11 19:32 ` syzbot
[not found] ` <20220312005624.1310-1-hdanton@sina.com>
2022-03-12 10:36 ` Pavel Skripkin [this message]
[not found] ` <20220312115854.1399-1-hdanton@sina.com>
2022-03-12 12:44 ` Pavel Skripkin
2021-06-22 15:43 syzbot
2021-06-22 16:07 ` Pavel Skripkin
2021-06-22 16:21 ` syzbot
2021-07-22 14:20 ` Krzysztof Kozlowski
2021-07-22 14:23 ` Krzysztof Kozlowski
2021-07-22 14:47 ` Alan Stern
2021-07-23 9:05 ` Krzysztof Kozlowski
2021-07-23 13:07 ` Alan Stern
2021-10-20 20:56 ` Krzysztof Kozlowski
2021-10-20 22:05 ` Alan Stern
2021-10-25 14:57 ` Krzysztof Kozlowski
2021-10-25 16:22 ` Alan Stern
2021-10-25 17:13 ` Krzysztof Kozlowski
2021-10-25 18:54 ` Alan Stern
2022-03-09 19:33 ` Pavel Skripkin
2022-03-09 19:56 ` syzbot
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=afbc1c26-8aea-e0b7-47e0-bee0d195a21b@gmail.com \
--to=paskripkin@gmail.com \
--cc=hdanton@sina.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+abd2e0dafb481b621869@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 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.