From: "Dae R. Jeong" <threeearcat@gmail.com>
To: Hillf Danton <hdanton@sina.com>
Cc: edumazet@google.com, pabeni@redhat.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: INFO: task hung in rfkill_unregister
Date: Wed, 5 Apr 2023 20:32:09 +0900 [thread overview]
Message-ID: <ZC1cObb9bAUKxdwu@dragonet> (raw)
In-Reply-To: <20230405111921.853-1-hdanton@sina.com>
On Wed, Apr 05, 2023 at 07:19:21PM +0800, Hillf Danton wrote:
> On 5 Apr 2023 19:39:56 +0900 "Dae R. Jeong" <threeearcat@gmail.com>
> > Hi,
> >
> > We observed an issue "INFO: task hung in rfkill_unregister" during fuzzing.
>
> Known issue [1].
>
> [1] https://lore.kernel.org/lkml/000000000000788a6905f0c06160@google.com/
Ah, I couldn't find it in the syzbot dashboard. Thank you for letting
me know it.
> > Unfortunately, we have not found a reproducer for the crash yet. We
> > will inform you if we have any update on this crash. Detailed crash
> > information is attached below.
> >
> > Best regards,
> > Dae R. Jeong
> >
> > -----
> > - Kernel version:
> > 6.2
>
> Curious why 6.2 is preferred over upstream given waste of time looking at 6.2
> today.
I'm sorry for wasting your time. I observed the issue before, but I
had my jobs to do (kernel development is not my main job) so I
reported it now with a small hope of being helpful. I will use the
upstream kernel when I try to find bugs later.
Best regards,
Dae R. Jeong
prev parent reply other threads:[~2023-04-05 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 10:39 INFO: task hung in rfkill_unregister Dae R. Jeong
[not found] ` <20230405111921.853-1-hdanton@sina.com>
2023-04-05 11:32 ` Dae R. Jeong [this message]
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=ZC1cObb9bAUKxdwu@dragonet \
--to=threeearcat@gmail.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).