All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yunseong Kim <ysk@kzalloc.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>, Taehee Yoo <ap420073@gmail.com>,
	Byungchul Park <byungchul@sk.com>,
	max.byungchul.park@gmail.com, yeoreum.yun@arm.com,
	ppbuk5246@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: [PATCH] net/nfc: Fix A-B/B-A deadlock between nfc_unregister_device and rfkill_fop_write
Date: Sun, 17 Aug 2025 07:45:51 +0200	[thread overview]
Message-ID: <7b6ff2bf-c2f3-411d-ab4a-a907d8edbc57@kernel.org> (raw)
In-Reply-To: <b8dc1074-725f-4048-9af5-6b62bd2150a3@kzalloc.com>

On 15/08/2025 10:23, Yunseong Kim wrote:
> Hi Krzysztof,
> 
> Thank you for your review.
> 
> On 8/15/25 2:55 PM, Krzysztof Kozlowski wrote:
>> On 14/08/2025 19:31, Yunseong Kim wrote:
>>> A potential deadlock due to A-B/B-A deadlock exists between the NFC core
>>> and the RFKill subsystem, involving the NFC device lock and the
>>> rfkill_global_mutex.
>>>
>>> This issue is particularly visible on PREEMPT_RT kernels, which can
>>> report the following warning:
>>
>> Why are not you crediting syzbot and its report?
>>
>> there is clear INSTRUCTION in that email from Syzbot.
> 
> I wanted to clarify that this report did not originate from syzbot.
> 
> I found this issue by building and running syzkaller locally on my own
> Arm64 RADXA Orion6 board.
> 
> This is reproduction series on my local syzkaller.
> 
> WARNING in __rt_mutex_slowlock
> 
> #	Log	Report	Time	Tag
> 7	log	report	2025/08/14 20:01	
> 6	log	report	2025/08/14 05:55	
> 5	log	report	2025/08/14 02:31	
> 4	log	report	2025/08/12 09:38	
> 3	log	report	2025/07/30 07:09	
> 2	log	report	2025/07/27 23:29	
> 1	log	report	2025/07/26 04:18	
> 0	log	report	2025/07/26 04:17
> 
> The reason this is coming from syzbot recently is that I worked with Sebastian,
> the RT maintainer, to fix KCOV to be PREEMPT_RT-aware. This was merged recently:
> Link: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-linus&id=9528d32873b38281ae105f2f5799e79ae9d086c2
> 
> So, syszbot now report it:
> https://syzkaller.appspot.com/bug?extid=535bbe83dfc3ae8d4be3


Syzbot reported it before you pasted patch, so it should also receive
the reported-by credit, even if you discovered it separately.

> 
>>> | rtmutex deadlock detected
>>> | WARNING: CPU: 0 PID: 22729 at kernel/locking/rtmutex.c:1674 rt_mutex_handle_deadlock+0x68/0xec kernel/locking/rtmutex.c:-1
>>> | Modules linked in:
>>> | CPU: 0 UID: 0 PID: 22729 Comm: syz.7.2187 Kdump: loaded Not tainted 6.17.0-rc1-00001-g1149a5db27c8-dirty #55 PREEMPT_RT
>>> | Hardware name: QEMU KVM Virtual Machine, BIOS 2025.02-8ubuntu1 06/11/2025
> 



Best regards,
Krzysztof

      reply	other threads:[~2025-08-17  5:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 17:31 [PATCH] net/nfc: Fix A-B/B-A deadlock between nfc_unregister_device and rfkill_fop_write Yunseong Kim
2025-08-15  5:55 ` Krzysztof Kozlowski
2025-08-15  8:23   ` Yunseong Kim
2025-08-17  5:45     ` Krzysztof Kozlowski [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=7b6ff2bf-c2f3-411d-ab4a-a907d8edbc57@kernel.org \
    --to=krzk@kernel.org \
    --cc=ap420073@gmail.com \
    --cc=byungchul@sk.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.byungchul.park@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ppbuk5246@gmail.com \
    --cc=syzkaller@googlegroups.com \
    --cc=yeoreum.yun@arm.com \
    --cc=ysk@kzalloc.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.