Re: [PATCH RFC 07/24] cleanup: Basic compatibility with capability analysis

2025-02-06 Thread Marco Elver
On Thu, 6 Feb 2025 at 22:29, Bart Van Assche wrote: > > On 2/6/25 10:10 AM, Marco Elver wrote: > > @@ -243,15 +243,18 @@ const volatile void * __must_check_fn(const volatile > > void *val) > > #define DEFINE_CLASS(_name, _type, _exit, _init, _init_args...) > > \ > > typedef _type

Re: [PATCH RFC 07/24] cleanup: Basic compatibility with capability analysis

2025-02-06 Thread Bart Van Assche
On 2/6/25 10:10 AM, Marco Elver wrote: @@ -243,15 +243,18 @@ const volatile void * __must_check_fn(const volatile void *val) #define DEFINE_CLASS(_name, _type, _exit, _init, _init_args...) \ typedef _type class_##_name##_t; \ static inlin

[PATCH RFC 07/24] cleanup: Basic compatibility with capability analysis

2025-02-06 Thread Marco Elver
Due to the scoped cleanup helpers used for lock guards wrapping acquire/release around their own constructors/destructors that store pointers to the passed locks in a separate struct, we currently cannot accurately annotate *destructors* which lock was released. While it's possible to annotate the