Re: [PATCH 5.10-stable 1/3] locking: Introduce __cleanup() based infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 30, 2024 at 11:30:51AM +0200, Lukas Wunner wrote:
> From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
> 
> commit 54da6a0924311c7cf5015533991e44fb8eb12773 upstream.
> 
> Use __attribute__((__cleanup__(func))) to build:
> 
>  - simple auto-release pointers using __free()
> 
>  - 'classes' with constructor and destructor semantics for
>    scope-based resource management.
> 
>  - lock guards based on the above classes.
> 
> Signed-off-by: Peter Zijlstra (Intel) <peterz@xxxxxxxxxxxxx>
> Signed-off-by: Lukas Wunner <lukas@xxxxxxxxx>
> Link: https://lkml.kernel.org/r/20230612093537.614161713%40infradead.org

Do we really want this in 5.10?  Are there any compiler versions that
5.10 still has to support that will break with this?

Same for 5.15.y, I'm loath to apply this to older kernels without loads
of testing.

thanks,

greg k-h




[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux