[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7bbe958c-0d25-4c68-b562-1c296b7311b7@ralfj.de>
Date: Wed, 26 Feb 2025 15:37:33 +0100
From: Ralf Jung <post@...fj.de>
To: James Bottomley <James.Bottomley@...senPartnership.com>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Ventura Jack <venturajack85@...il.com>
Cc: 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, gregkh@...uxfoundation.org, hch@...radead.org,
ksummit@...ts.linux.dev, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org
Subject: Re: C aggregate passing (Rust kernel policy)
On 26.02.25 15:26, 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.
Rust panics typically print a backtrace even if they don't unwind. This works
just fine in userland, but I don't know the state in the kernel.
Kind regards,
Ralf
Powered by blists - more mailing lists