[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260121134037.kh3rfrgmwsylcl5r@inspiron>
Date: Wed, 21 Jan 2026 19:10:37 +0530
From: Prithvi <activprithvi@...il.com>
To: Bart Van Assche <bvanassche@....org>
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 Tue, Jan 20, 2026 at 05:48:16AM -0800, Bart Van Assche wrote:
> 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.
Sure. I will make v2 patch for the same.
Thanks,
Prithvi
Powered by blists - more mailing lists