linux-kernel - Re: [GIT PULL] Rust for 6.16

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: <CAHk-=wik7gvxt-CEak_4HsGziRwo6-7q9LGeW37Pj9182dJ=ow@mail.gmail.com>
Date: Wed, 4 Jun 2025 21:18:36 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Miguel Ojeda <ojeda@...nel.org>
Cc: Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>, 
	Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, 
	Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Rust for 6.16

On Wed, 4 Jun 2025 at 19:54, Miguel Ojeda <ojeda@...nel.org> wrote:
>
> There are a few conflicts, including semantic ones, but they are all
> easy to apply. The resolutions in the latest linux-next are fine; I also
> did a test merge -- please check either to catch the semantic ones

Hmm. I don't understand why the suggested merge adds those

        let self_ptr: *mut Opaque<bindings::drm_gem_object> = self_ptr.cast();

        let ptr: *mut Opaque<bindings::drm_gem_object> = obj.cast();

cases to rust/kernel/drm/gem/mod.rs, and it built cleanly for me
without those changes, but that may be because my build doesn't
trigger this.

But in the name of safety, and because I didn't understand that
change, I modified my merge to do what you did.

                 Linus