linux-kernel - Re: [for-next][PATCH 01/15] tracing: Switch trace.c code over to use guard()

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: <d87cb12a-db58-4ff3-999e-c99839524e8e@web.de>
Date: Sat, 28 Dec 2024 11:40:26 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Steven Rostedt <rostedt@...dmis.org>, linux-trace-kernel@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org,
 Andrew Morton <akpm@...ux-foundation.org>,
 Mark Rutland <mark.rutland@....com>, Masami Hiramatsu <mhiramat@...nel.org>,
 Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
 Peter Zijlstra <peterz@...radead.org>
Subject: Re: [for-next][PATCH 01/15] tracing: Switch trace.c code over to use
 guard()

…
> Switch every location that ends with unlocking a mutex or freeing on error
> over to using the guard(mutex)() and __free() infrastructure

Do any contributors find it safer and cleaner to separate adjustments for
these programming interfaces?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.13-rc4#n81


>                                                              to let the
> compiler worry about releasing locks. …

May the compiler take care of further code transformation concerns?

Regards,
Markus