[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025022611-work-sandal-2759@gregkh>
Date: Wed, 26 Feb 2025 15:39:55 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: James Bottomley <James.Bottomley@...senpartnership.com>
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, 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.
Try it and see!
Powered by blists - more mailing lists