Changes in try_from_bytes.rs

29b2a2b99a4dbb9849769162754ed53abbfd40c2 - rust: zerocopy-derive: avoid generating non-ASCII identifiers

Mon, 08 Jun 2026 16:14:34 +0200

rust: zerocopy-derive: avoid generating non-ASCII identifiersLinux is built with `-Dnon_ascii_idents`. However, `zerocopy-derive`uses a non-ASCII character (`ẕ`) internally, which in turn triggersthe lint when attempting to use derives like `FromBytes`: error: identifier contains non-ASCII characters --> rust/kernel/lib.rs:153:9 | 153 | a: u32, | ^ | = note: requested on the command line with `-D non-ascii-idents`This was already noticed by another project using`#![deny(non_ascii_idents)]` [1]. `zerocopy` added an`#[allow(non_ascii_idents)]` [2], but it does not work since, at themoment, the `non_ascii_idents` lint is a `crate_level_only` one, and thus`allow`s only work at the crate root level.Due to this, an issue about relaxing this restriction was created inupstream Rust [3] some months ago.Thus work around it here by using another prefix. The likelihood of acollision is very small for us, since we control the callers, and thiswill hopefully be fixed soon at either the `zerocopy` or the Rust level.I filed an issue [4] about it with upstream `zerocopy` as requestedand we discussed this with upstream Rust and `zerocopy`: the Rust issuegot nominated and a PR [5] to relax the restriction was submitted byJoshua. Upstream `zerocopy` prefers that approach, so if Rust merges it,then it means we will be able to remove the workaround when we bump theMSRV, thus likely late 2027, since we follow Debian Stable.Cc: Joshua Liebow-Feeser Cc: Jack Wrenn Link: https://github.com/google/zerocopy/issues/2880 [1]Link: https://github.com/google/zerocopy/pull/2882 [2]Link: https://github.com/rust-lang/rust/issues/151025 [3]Link: https://github.com/google/zerocopy/issues/3427 [4]Link: https://github.com/rust-lang/rust/pull/157497 [5]Link: https://patch.msgid.link/20260608141439.182634-16-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux/rust/zerocopy-derive/derive/try_from_bytes.rs

5f85604cf0877b0369dfd68cd50cf61c0f134819 - rust: zerocopy-derive: add SPDX License Identifiers

Mon, 08 Jun 2026 16:14:33 +0200

rust: zerocopy-derive: add SPDX License IdentifiersOriginally, when the Rust upstream `alloc` standard library crate wasvendored, the SPDX License Identifiers were added to every file so thatthe license on those was clear. The same happened with the vendoring of`proc_macro2`, `quote` and `syn`. Please see: commit 057b8d257107 ("rust: adapt `alloc` crate to the kernel") commit 69942c0a8965 ("rust: syn: add SPDX License Identifiers") commit ddfa1b279d08 ("rust: quote: add SPDX License Identifiers") commit a9acfceb9614 ("rust: proc-macro2: add SPDX License Identifiers")Thus do the same for the `zerocopy-derive` crate.This makes `scripts/spdxcheck.py` pass: use parentheses like commit06e9bfc1e57d ("ionic: make spdxcheck.py happy") did since we have two`OR` operators in the expression (three licenses).Finally, as requested, I filed an issue [1] with upstream about it.Cc: Joshua Liebow-Feeser Cc: Jack Wrenn Link: https://github.com/google/zerocopy/issues/3428 [1]Link: https://patch.msgid.link/20260608141439.182634-15-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux/rust/zerocopy-derive/derive/try_from_bytes.rs

b437b3832874d4df88195d31b9052417674ffaed - rust: zerocopy-derive: import crate

Mon, 08 Jun 2026 16:14:32 +0200

rust: zerocopy-derive: import crateThis is a subset of the Rust `zerocopy-derive` crate, version v0.8.50(released 2026-05-31), licensed under "BSD-2-Clause OR Apache-2.0 ORMIT", from: https://github.com/google/zerocopy/tree/v0.8.50/zerocopy-derive/srcThe files are copied as-is, with no modifications whatsoever (not evenadding the SPDX identifiers).For copyright details, please see: https://github.com/google/zerocopy/blob/v0.8.50/README.md?plain=1 https://github.com/google/zerocopy/blob/v0.8.50/LICENSE-BSD https://github.com/google/zerocopy/blob/v0.8.50/LICENSE-APACHE https://github.com/google/zerocopy/blob/v0.8.50/LICENSE-MITThe next two patches modify these files as needed for use within thekernel. This patch split allows reviewers to double-check the importand to clearly see the differences introduced.The following script may be used to verify the contents: for path in $(cd rust/zerocopy-derive/ && find . -type f); do curl --silent --show-error --location \ https://github.com/google/zerocopy/raw/v0.8.50/zerocopy-derive/src/$path \ | diff --unified rust/zerocopy-derive/$path - && echo $path: OK doneCc: Joshua Liebow-Feeser Cc: Jack Wrenn Link: https://patch.msgid.link/20260608141439.182634-14-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux/rust/zerocopy-derive/derive/try_from_bytes.rs