linux-kernel - Re: C aggregate passing (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: <16127450a24e9df8112a347fe5f6df9c9cca2926.camel@HansenPartnership.com>
Date: Wed, 26 Feb 2025 09:45:53 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, Ventura Jack
 <venturajack85@...il.com>, Kent Overstreet <kent.overstreet@...ux.dev>, "H.
 Peter Anvin" <hpa@...or.com>, Alice Ryhl <aliceryhl@...gle.com>, Linus
 Torvalds <torvalds@...ux-foundation.org>, Gary Guo <gary@...yguo.net>,
 airlied@...il.com,  boqun.feng@...il.com, david.laight.linux@...il.com,
 ej@...i.de, hch@...radead.org,  ksummit@...ts.linux.dev,
 linux-kernel@...r.kernel.org,  rust-for-linux@...r.kernel.org, Ralf Jung
 <post@...fj.de>
Subject: Re: C aggregate passing (Rust kernel policy)

On Wed, 2025-02-26 at 15:39 +0100, Greg KH wrote:
> On Wed, Feb 26, 2025 at 09:26:50AM -0500, James Bottomley wrote:
> > On Wed, 2025-02-26 at 14:53 +0100, Miguel Ojeda wrote:
> > > On Wed, Feb 26, 2025 at 2:03 PM Ventura Jack
> > > <venturajack85@...il.com> wrote:
> > [...]
> > > > Exception/unwind safety may be another subject that increases
> > > > the difficulty of writing unsafe Rust.
> > > 
> > > Note that Rust panics in the kernel do not unwind.
> > 
> > I presume someone is working on this, right?  While rust isn't
> > pervasive enough yet for this to cause a problem, dumping a
> > backtrace is one of the key things we need to diagnose how
> > something went wrong, particularly for user bug reports where they
> > can't seem to bisect.
> 
> The backtrace is there, just like any other call to BUG() provides,
> which is what the rust framework calls for this.

>From some other rust boot system work, I know that the quality of a
simple backtrace in rust where you just pick out addresses you think
you know in the stack and print them as symbols can sometimes be rather
misleading, which is why you need an unwinder to tell you exactly what
happened.

Regards,

James