[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ac604919-1620-4fea-9401-869fd15f3533@acm.org>
Date: Tue, 20 Jan 2026 05:48:16 -0800
From: Bart Van Assche <bvanassche@....org>
To: Prithvi <activprithvi@...il.com>
Cc: martin.petersen@...cle.com, linux-scsi@...r.kernel.org,
target-devel@...r.kernel.org, linux-kernel@...r.kernel.org, hch@....de,
jlbec@...lplan.org, linux-fsdevel@...r.kernel.org,
linux-kernel-mentees@...ts.linux.dev, skhan@...uxfoundation.org,
david.hunter.linux@...il.com, khalid@...nel.org,
syzbot+f6e8174215573a84b797@...kaller.appspotmail.com, stable@...r.kernel.org
Subject: Re: [PATCH] scsi: target: Fix recursive locking in
__configfs_open_file()
On 1/19/26 10:50 AM, Prithvi wrote:
> Possible unsafe locking scenario:
>
> CPU0
> ----
> lock(&p->frag_sem);
> lock(&p->frag_sem);
The least intrusive way to suppress this type of lockdep complaints is
by using lockdep_register_key() and lockdep_unregister_key().
Thanks,
Bart.
Powered by blists - more mailing lists