linux-kernel - Re: [RFC PATCH] drm: panthor: add dev

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: <CANiq72=J=RVRy+f8+B=Eb_J6sNBsGqvBT8-io-m+VqJNgZRnkw@mail.gmail.com>
Date: Sat, 13 Jul 2024 10:17:03 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Dave Airlie <airlied@...il.com>
Cc: Danilo Krummrich <dakr@...hat.com>, Daniel Almeida <daniel.almeida@...labora.com>, 
	Steven Price <steven.price@....com>, Wedson Almeida Filho <wedsonaf@...il.com>, ojeda@...nel.org, 
	lyude@...hat.com, robh@...nel.org, lina@...hilina.net, mcanal@...lia.com, 
	rust-for-linux@...r.kernel.org, dri-devel@...ts.freedesktop.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] drm: panthor: add dev_coredumpv support

On Sat, Jul 13, 2024 at 2:48 AM Dave Airlie <airlied@...il.com> wrote:
>
> I think I'm on the uapi should remain in C for now, we define uapi
> types with the kernel types and we have downstream tools to scan and
> parse them to deal with alignments and padding (I know FEX relies on
> it), so I think we should be bindgen from uapi headers into rust for
> now. There might be a future where this changes, but that isn't now
> and I definitely don't want to mix C and rust uapi in one driver.

Agreed, I think with what you say here (changes required to external
tooling), even if the generation was done by `rustc` itself and
guaranteed to be stable, it would still be impractical at this point
in time.

Cheers,
Miguel