linux-kernel - linux-next: manual merge of the rust tree with the opp tree

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-next>] [day] [month] [year] [list]

Message-ID: <20251023124926.35a9ded0@canb.auug.org.au>
Date: Thu, 23 Oct 2025 12:49:26 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Miguel Ojeda <ojeda@...nel.org>, Viresh Kumar <viresh.kumar@...aro.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, Tamir Duberstein
 <tamird@...il.com>
Subject: linux-next: manual merge of the rust tree with the opp tree

Hi all,

Today's linux-next merge of the rust tree got a conflict in:

  rust/kernel/opp.rs

between commit:

  e6fdbe8feace ("rust: opp: fix broken rustdoc link")

from the opp tree and commit:

  965a39a9627b ("rust: opp: use `CStr::as_char_ptr`")

from the rust tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc rust/kernel/opp.rs
index 04472a8de3ff,9d6c58178a6f..000000000000
--- a/rust/kernel/opp.rs
+++ b/rust/kernel/opp.rs
@@@ -87,8 -87,8 +87,8 @@@ use core::{marker::PhantomData, ptr}
  
  use macros::vtable;
  
 -/// Creates a null-terminated slice of pointers to [`Cstring`]s.
 +/// Creates a null-terminated slice of pointers to [`CString`]s.
- fn to_c_str_array(names: &[CString]) -> Result<KVec<*const u8>> {
+ fn to_c_str_array(names: &[CString]) -> Result<KVec<*const c_char>> {
      // Allocated a null-terminated vector of pointers.
      let mut list = KVec::with_capacity(names.len() + 1, GFP_KERNEL)?;
  

Content of type "application/pgp-signature" skipped