linux-kernel - Re: [PATCH v14 26/34] cxl: Change CXL handlers to use guard() instead of scoped

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f441aee5-7313-4d5e-95cc-3caa4d12ce2a@web.de>
Date: Fri, 23 Jan 2026 11:05:07 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Terry Bowman <terry.bowman@....com>, linux-pci@...r.kernel.org,
 linux-cxl@...r.kernel.org, Alejandro Lucero Palau <alucerop@....com>,
 Alison Schofield <alison.schofield@...el.com>,
 Benjamin Cheatham <benjamin.cheatham@....com>,
 Bjorn Helgaas <bhelgaas@...gle.com>, Dan Carpenter
 <dan.carpenter@...aro.org>, Dan Williams <dan.j.williams@...el.com>,
 Dave Jiang <dave.jiang@...el.com>, Davidlohr Bueso <dave@...olabs.net>,
 Ira Weiny <ira.weiny@...el.com>,
 Jonathan Cameron <Jonathan.Cameron@...wei.com>,
 Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>,
 Lukas Wunner <lukas@...ner.de>, Li Ming <ming.li@...omail.com>,
 Pradeep Vinesh Reddy Kodamati <PradeepVineshReddy.Kodamati@....com>,
 Robert Richter <rrichter@....com>, Shiju Jose <shiju.jose@...wei.com>,
 Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
 Vishal Verma <vishal.l.verma@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v14 26/34] cxl: Change CXL handlers to use guard() instead
 of scoped_guard()

> The CXL protocol error handlers use scoped_guard() to guarantee access to
> the underlying CXL memory device. Improve readability and reduce complexity
> by changing the current scoped_guard() to be guard().

Would it be worth to mention that this adjustment can only be performed
because lock scopes can be kept the same for two function implementations?

Regards,
Markus