[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAo+4rXMsmUBcTvzQrBjz+4ey-W=UToGps6esfBZGq-1ji96Gg@mail.gmail.com>
Date: Sun, 18 Jan 2026 16:26:00 +0800
From: Chengfeng Ye <dg573847474@...il.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: linux-scsi@...r.kernel.org, MPT-FusionLinux.pdl@...adcom.com,
James Bottomley <James.Bottomley@...senpartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>, Sathya Prakash <sathya.prakash@...adcom.com>,
Sreekanth Reddy <sreekanth.reddy@...adcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@...adcom.com>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: scsi: mpt3sas: Fix use-after-free race in event log access
> How do you think about to increase the application of scope-based resource management
> occasionally also any more source code places?
Thanks for your suggestion on it. I think it is a very good practice
to get rid of problems like
lock-leak or double-locking, while keeping the code elegant.
I would certainly like to keep the practice while making my future
patch, and help adjust other
code to also use the scope-based locking when appropriate.
Best regards,
Chengfeng
Powered by blists - more mailing lists