[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2f88aa9b-b1c2-4b02-81e8-1c43b982db1b@acm.org>
Date: Thu, 15 Jan 2026 08:57:28 -0800
From: Bart Van Assche <bvanassche@....org>
To: Prithvi Tambewagh <activprithvi@...il.com>, martin.petersen@...cle.com
Cc: 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/8/26 12:15 PM, Prithvi Tambewagh wrote:
> This poses a possibility of recursive locking,
> which triggers the lockdep warning.
Patches that fix a lockdep complaint should include the full lockdep
complaint.
Since the fixed lockdep complaint didn't trigger a deadlock it must be
a false positive complaint, isn't it? Such complaints should be fixed
but without additional information we can't tell what the best way is to
fix the complaint.
Thanks,
Bart.
Powered by blists - more mailing lists