From: Johannes Berg <johannes@sipsolutions.net>
To: syzbot <syzbot+bb540a4bbfb4ae3b425d@syzkaller.appspotmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Bongsu Jeon <bongsu.jeon@samsung.com>
Subject: Re: [syzbot] [wireless?] INFO: task hung in rfkill_unregister (3)
Date: Wed, 07 Jun 2023 12:22:12 +0200 [thread overview]
Message-ID: <81ea9426dca43f7a74507b9fa70ab217359a3eb1.camel@sipsolutions.net> (raw)
In-Reply-To: <00000000000052748d05fd872fb0@google.com>
On Wed, 2023-06-07 at 02:58 -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: eb0f1697d729 Merge branch 'for-next/core', remote-tracking..
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=17b656a5280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=8860074b9a9d6c45
> dashboard link: https://syzkaller.appspot.com/bug?extid=bb540a4bbfb4ae3b425d
> compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: arm64
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=122665a3280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13dc1c59280000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/034232da7cff/disk-eb0f1697.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/b11411bec33e/vmlinux-eb0f1697.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/a53c52e170dd/Image-eb0f1697.gz.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+bb540a4bbfb4ae3b425d@syzkaller.appspotmail.com
>
> INFO: task syz-executor410:6034 blocked for more than 143 seconds.
> Not tainted 6.4.0-rc3-syzkaller-geb0f1697d729 #0
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:syz-executor410 state:D stack:0 pid:6034 ppid:5996 flags:0x0000000c
> Call trace:
> __switch_to+0x320/0x754 arch/arm64/kernel/process.c:556
> context_switch kernel/sched/core.c:5343 [inline]
> __schedule+0x1368/0x23b8 kernel/sched/core.c:6669
> schedule+0xc4/0x170 kernel/sched/core.c:6745
> schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6804
> __mutex_lock_common+0xbd8/0x21a0 kernel/locking/mutex.c:679
> __mutex_lock kernel/locking/mutex.c:747 [inline]
> mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:799
> rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
> nfc_unregister_device+0x98/0x290 net/nfc/core.c:1167
> nci_unregister_device+0x1dc/0x21c net/nfc/nci/core.c:1303
> virtual_ncidev_close+0x5c/0xa0 drivers/nfc/virtual_ncidev.c:163
This seems like an issue with the virtual NFC device. I feel we had this
before?
johannes
prev parent reply other threads:[~2023-06-07 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 9:58 [syzbot] [wireless?] INFO: task hung in rfkill_unregister (3) syzbot
2023-06-07 10:22 ` Johannes Berg [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=81ea9426dca43f7a74507b9fa70ab217359a3eb1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bongsu.jeon@samsung.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+bb540a4bbfb4ae3b425d@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;
as well as URLs for NNTP newsgroup(s).