linux-kernel - Re: Rust kernel policy

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: <20250219101353.32bed6c9@gandalf.local.home>
Date: Wed, 19 Feb 2025 10:13:53 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Dan Carpenter <dan.carpenter@...aro.org>, Christoph Hellwig 
 <hch@...radead.org>, Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
 rust-for-linux <rust-for-linux@...r.kernel.org>, Linus Torvalds
 <torvalds@...ux-foundation.org>, Greg KH <gregkh@...uxfoundation.org>,
 David Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
 ksummit@...ts.linux.dev
Subject: Re: Rust kernel policy

On Wed, 19 Feb 2025 09:14:17 -0500
James Bottomley <James.Bottomley@...senPartnership.com> wrote:

> I look at most of the bugfixes flowing through subsystems I watch and a
> lot of them are in error legs.  Usually around kfree cockups (either
> forgetting or freeing to early).  Could we possibly fix a lot of this
> by adopting the _cleanup_ annotations[1]?  I've been working in systemd
> code recently and they seem to make great use of this for error leg
> simplification.

And the tracing subsystem has already been moving in that direction.

  https://lore.kernel.org/all/20241219201158.193821672@goodmis.org/
  https://lore.kernel.org/all/173630223453.1453474.6442447279377996686.stgit@devnote2/

I need to add this logic to my tracing libraries too. That's on my TODO list.

-- Steve