… > v11: … > - Use guard(mutex) > > v12: > - Revert to mutex_lock/mutex_unlock in iio_buffer_attach_dmabuf(), > as it uses cleanup GOTOs … I would find it nice if better design options could gain acceptance. Will the chances grow to adjust scopes another bit for involved variables in such function implementations? A) Enclosing a source code part with extra curly brackets? B) scoped_guard()? https://elixir.bootlin.com/linux/v6.10-rc4/source/include/linux/cleanup.h#L137 C) Moving a locked source code part into a separate function implementation? Regards, Markus