mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Magnus Leatti <magnusleatti@kernelriot.com>
To: syzbot+3e3c2f8ca188e30b1427@syzkaller.appspotmail.com
Cc: syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, oe-linux-nfc@lists.linux.dev,
	David Heidelberg <david@ixit.cz>,
	Johannes Berg <johannes@sipsolutions.net>,
	Deepanshu Kartikey <kartikey406@gmail.com>
Subject: Re: [syzbot] INFO: task hung in nfc_rfkill_set_block
Date: Thu, 12 Nov 2026 06:02:17 -0300	[thread overview]
Message-ID: <20261112090217.1462672-1-magnusleatti@kernelriot.com> (raw)
In-Reply-To: <000000000000959f6b05ed853d12@google.com>

Hi,

This looks like the device_lock vs rfkill_global_mutex inversion
fixed by 1ab526d97a57 ("net: nfc: fix deadlock between
nfc_unregister_device and rfkill_fop_write"). That fix credited a
different syzbot report, so this one was never linked to it.

I ran the C reproducer for 600 s per kernel, x86_64 under QEMU/KVM:

  1ab526d97a57^  hung task report at 91 s (rfkill_sync_work in
                 nfc_dev_down, nfc_unregister_device in
                 rfkill_unregister)
  1ab526d97a57   no hang
  9d66f26fefac   no hang (mainline)

#syz fix: net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write

Thanks,
Magnus

  parent reply	other threads:[~2026-11-12  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 16:56 syzbot
2023-05-24  5:43 ` [syzbot] [nfc?] " syzbot
2023-11-21 10:55 ` [syzbot] [net?] " syzbot
2026-11-12  9:02 ` Magnus Leatti [this message]
     [not found] <20221116050320.2937-1-hdanton@sina.com>
2022-11-16  6:22 ` [syzbot] " 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=20261112090217.1462672-1-magnusleatti@kernelriot.com \
    --to=magnusleatti@kernelriot.com \
    --cc=david@ixit.cz \
    --cc=johannes@sipsolutions.net \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-linux-nfc@lists.linux.dev \
    --cc=syzbot+3e3c2f8ca188e30b1427@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®