From: Johannes Berg <johannes@sipsolutions.net>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: syzbot+50499e163bfa302dfe7b@syzkaller.appspotmail.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [syzbot] [wireless?] INFO: task hung in rfkill_global_led_trigger_worker (3)
Date: Fri, 19 Jul 2024 09:30:10 -0700 [thread overview]
Message-ID: <c9f8412dac004da0a192376a235ced2412299fb8.camel@sipsolutions.net> (raw)
In-Reply-To: <15930e85-3b82-4119-b1ef-d899ac03fa3d@I-love.SAKURA.ne.jp>
On Fri, 2024-07-19 at 22:59 +0900, Tetsuo Handa wrote:
> This is a deadlock which lockdep cannot detect.
> Please check which lock should be taken first.
>
> 2 locks held by syz.1.2508/23558:
> #0: ffff88805ff4f100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:1009 [inline]
> #0: ffff88805ff4f100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x63/0x2a0 net/nfc/core.c:1165
> #1: ffffffff8f8e1b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xd0/0x230 net/rfkill/core.c:1149
> 2 locks held by syz.4.2510/23544:
> #0: ffffffff8f8e1b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a9/0x790 net/rfkill/core.c:1297
> #1: ffff88805ff4f100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:1009 [inline]
> #1: ffff88805ff4f100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
> #1: ffff88805ff4f100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x310 net/nfc/core.c:179
Yeah, this is a well-known issue; I believe this should be fixed in the
NFC (virtual) device.
johannes
next prev parent reply other threads:[~2024-07-19 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 13:15 syzbot
2024-07-19 13:59 ` Tetsuo Handa
2024-07-19 16:30 ` Johannes Berg [this message]
2024-09-23 20:03 ` syzbot
2025-06-17 10:11 ` Johannes Berg
2025-06-17 10:11 ` 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=c9f8412dac004da0a192376a235ced2412299fb8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=syzbot+50499e163bfa302dfe7b@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
all inboxes | Powered by JetHome®