[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z7bQRvHNcK_MmDQn@infradead.org>
Date: Wed, 19 Feb 2025 22:48:38 -0800
From: Christoph Hellwig <hch@...radead.org>
To: James Bottomley <James.Bottomley@...senpartnership.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Christoph Hellwig <hch@...radead.org>,
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, Feb 19, 2025 at 11:03:28AM -0500, James Bottomley wrote:
> > This has come up a few times, and we indeed would like to have some
> > annotations in the C headers so that we can generate more (and to
> > keep the information local).
> >
> > For instance, it would be nice to have bindgen's `__opaque` near the
> > C items, or being able to mark functions as `__safe`, or to have
> > other `enum`s-related annotations, or even custom attributes, as well
> > as "formatted-formally-enough" docs so that can be rendered properly
> > on the Rust side, or even references/lifetimes with an eventual "Safe
> > C"-like approach, and so on and so forth.
> >
> > However, even if we automate more and even reach a point where most C
> > APIs are e.g. "safe" (which would be great),
>
> I wouldn't say C API safety would be the main goal, although it might
> be a nice add on feature.
Why not? Why is safety suddenly less a goal when you don't use the
right syntactic sugar?
Powered by blists - more mailing lists