8000 Tags · Rust-for-Linux/linux · GitHub
[go: up one dir, main page]

Skip to content

Tags: Rust-for-Linux/linux

Tags

pin-init-v6.17-result-blanket

Toggle pin-init-v6.17-result-blanket's commit message
pin-init blanket implementation changes for v6.17

Remove the error from the blanket implementations for `[Pin]Init` and
add implementations for `Result`.

rust-fixes-6.16

Toggle rust-fixes-6.16's commit message

Verified

This tag was signed with the committer’s verified signature.
ojeda Miguel Ojeda
Rust fixes for v6.16

'kernel' crate:

  - 'hrtimer': fix future compile error when the 'impl_has_hr_timer!'
    macro starts to get called.

v6.16-rc1

Toggle v6.16-rc1's commit message
Linux 6.16-rc1

rust-6.16

Toggle rust-6.16's commit message

Verified

This tag was signed with the committer’s verified signature.
ojeda Miguel Ojeda
Rust changes for v6.16

Toolchain and infrastructure:

 - KUnit '#[test]'s:

   - Support KUnit-mapped 'assert!' macros.

     The support that landed last cycle was very basic, and the
     'assert!' macros panicked since they were the standard library
     ones. Now, they are mapped to the KUnit ones in a similar way to
     how is done for doctests, reusing the infrastructure there.

     With this, a failing test like:

         #[test]
         fn my_first_test() {
             assert_eq!(42, 43);
         }

     will report:

         # my_first_test: ASSERTION FAILED at rust/kernel/lib.rs:251
         Expected 42 == 43 to be true, but is false
         # my_first_test.speed: normal
         not ok 1 my_first_test

   - Support tests with checked 'Result' return types.

     The return value of test functions that return a 'Result' will be
     checked, thus one can now easily catch errors when e.g. using the
     '?' operator in tests.

     With this, a failing test like:

         #[test]
         fn my_test() -> Result {
             f()?;
             Ok(())
         }

     will report:

         # my_test: ASSERTION FAILED at rust/kernel/lib.rs:321
         Expected is_test_result_ok(my_test()) to be true, but is false
         # my_test.speed: normal
         not ok 1 my_test

   - Add 'kunit_tests' to the prelude.

 - Clarify the remaining language unstable features in use.

 - Compile 'core' with edition 2024 for Rust >= 1.87.

 - Workaround 'bindgen' issue with forward references to 'enum' types.

 - objtool: relax slice condition to cover more 'noreturn' functions.

 - Use absolute paths in macros referencing 'core' and 'kernel' crates.

 - Skip '-mno-fdpic' flag for bindgen in GCC 32-bit arm builds.

 - Clean some 'doc_markdown' lint hits -- we may enable it later on.

'kernel' crate:

 - 'alloc' module:

   - 'Box': support for type coercion, e.g. 'Box<T>' to 'Box<dyn U>' if
     'T' implements 'U'.

   - 'Vec': implement new methods (prerequisites for nova-core and
     binder): 'truncate', 'resize', 'clear', 'pop',
     'push_within_capacity' (with new error type 'PushError'),
     'drain_all', 'retain', 'remove' (with new error type
     'RemoveError'), insert_within_capacity' (with new error type
     'InsertError').

     In addition, simplify 'push' using 'spare_capacity_mut', split
     'set_len' into 'inc_len' and 'dec_len', add type invariant
     'len <= capacity' and simplify 'truncate' using 'dec_len'.

 - 'time' module:

   - Morph the Rust hrtimer subsystem into the Rust timekeeping
     subsystem, covering delay, sleep, timekeeping, timers. This new
     subsystem has all the relevant timekeeping C maintainers listed in
     the entry.

   - Replace 'Ktime' with 'Delta' and 'Instant' types to represent a
     duration of time and a point in time.

   - Temporarily add 'Ktime' to 'hrtimer' module to allow 'hrtimer' to
     delay converting to 'Instant' and 'Delta'.

 - 'xarray' module:

   - Add a Rust abstraction for the 'xarray' data structure. This
     abstraction allows Rust code to leverage the 'xarray' to store
     types that implement 'ForeignOwnable'. This support is a dependency
     for memory backing feature of the Rust null block driver, which is
     waiting to be merged.

   - Set up an entry in 'MAINTAINERS' for the XArray Rust support.
     Patches will go to the new Rust XArray tree and then via the Rust
     subsystem tree for now.

   - Allow 'ForeignOwnable' to carry information about the pointed-to
     type. This helps asserting alignment requirements for the pointer
     passed to the foreign language.

 - 'container_of!': retain pointer mut-ness and add a compile-time check
   of the type of the first parameter ('$field_ptr').

 - Support optional message in 'static_assert!'.

 - Add C FFI types (e.g. 'c_int') to the prelude.

 - 'str' module: simplify KUnit tests 'format!' macro, convert
   'rusttest' tests into KUnit, take advantage of the '-> Result'
   support in KUnit '#[test]'s.

 - 'list' module: add examples for 'List', fix path of 'assert_pinned!'
   (so far unused macro rule).

 - 'workqueue' module: remove 'HasWork::OFFSET'.

 - 'page' module: add 'inline' attribute.

'macros' crate:

 - 'module' macro: place 'cleanup_module()' in '.exit.text' section.

'pin-init' crate:

 - Add 'Wrapper<T>' trait for creating pin-initializers for wrapper
   structs with a structurally pinned value such as 'UnsafeCell<T>' or
   'MaybeUninit<T>'.

 - Add 'MaybeZeroable' derive macro to try to derive 'Zeroable', but
   not error if not all fields implement it. This is needed to derive
   'Zeroable' for all bindgen-generated structs.

 - Add 'unsafe fn cast_[pin_]init()' functions to unsafely change the
   initialized type of an initializer. These are utilized by the
   'Wrapper<T>' implementations.

 - Add support for visibility in 'Zeroable' derive macro.

 - Add support for 'union's in 'Zeroable' derive macro.

 - Upstream dev news: streamline CI, fix some bugs. Add new workflows
   to check if the user-space version and the one in the kernel tree
   have diverged. Use the issues tab [1] to track them, which should
   help folks report and diagnose issues w.r.t. 'pin-init' better.

     [1] https://github.com/rust-for-linux/pin-init/issues

Documentation:

 - Testing: add docs on the new KUnit '#[test]' tests.

 - Coding guidelines: explain that '///' vs. '//' applies to private
   items too. Add section on C FFI types.

 - Quick Start guide: update Ubuntu instructions and split them into
   "25.04" and "24.04 LTS and older".

And a few other cleanups and improvements.

alloc-next-v6.16-2025-05-13

Toggle alloc-next-v6.16-2025-05-13's commit message
Alloc changes for v6.16

Box:
  - support for type coercion, e.g. `Box<T>` to `Box<dyn U>` if T
    implements U

Vec:
  - implement new methods (prerequisites for nova-core and binder)
    - Vec::truncate()
    - Vec::resize()
    - Vec::clear()
    - Vec::pop()
    - Vec::push_within_capacity()
      - new error type: PushError
    - Vec::drain_all()
    - Vec::retain()
    - Vec::remove()
      - new error type: RemoveError
    - Vec::insert_within_capacity
      - new error type: InsertError
  - simplify Vec::push() using Vec::spare_capacity_mut()
  - split Vec::set_len() into Vec::inc_len() and Vec::dec_len()
    - add type invariant Vec::len() <= Vec::capacity
    - simplify Vec::truncate() using Vec::dec_len()

rust-fixes-6.15-2

Toggle rust-fixes-6.15-2's commit message

Verified

This tag was signed with the committer’s verified signature.
ojeda Miguel Ojeda
Rust fixes for v6.15 (2nd)

Toolchain and infrastructure:

 - Make CFI_AUTO_DEFAULT depend on !RUST or Rust >= 1.88.0.

 - Clean Rust (and Clippy) lints for the upcoming Rust 1.87.0 and Rust
   1.88.0 releases.

 - Clean objtool warning for the upcoming Rust 1.87.0 release by adding
   one more noreturn function.

rust-xarray-for-v6.16

Toggle rust-xarray-for-v6.16's commit message
Rust xarray API for v6.16

Introduce Rust support for the `xarray` data structure:

 - Add a rust abstraction for the `xarray` data structure. This abstraction
   allows rust code to leverage the `xarray` to store types that implement
   `ForeignOwnable`. This support is a dependency for memory backing feature of
   the rust null block driver, which is waiting to be merged.

 - Set up an entry in MAINTAINERS for the xarray rust support. Patches will go
   to the new rust xarray tree and then via the rust subsystem tree for now.

`kernel` crate:

 - Allow `ForeignOwnable` to carry information about the pointed-to type. This
   helps asserting alignment requirements for the pointer passed to the foreign
   language.

rust-timekeeping-for-v6.16

Toggle rust-timekeeping-for-v6.16's commit message
Rust timekeeping changes for v6.16

 - Replace `Ktime` with `Delta` and `Instant` types to represent a duration of
   time and a point in time.

 - Temporarily add `Ktime` to `hrtimer` module to allow `hrtimer` to delay
   converting to `Instant` and `Delta`.

rust-timekeeping-for-v6.16-v2

Toggle rust-timekeeping-for-v6.16-v2's commit message
Rust timekeeping changes for v6.16

 - Morph the rust hrtimer subsystem into the rust timekeeping subsystem,
   covering delay, sleep, timekeeping, timers. This new subsystem has all the
   relevant timekeeping C maintainers listed in the entry.

 - Replace `Ktime` with `Delta` and `Instant` types to represent a duration of
   time and a point in time.

 - Temporarily add `Ktime` to `hrtimer` module to allow `hrtimer` to delay
   converting to `Instant` and `Delta`.

pin-init-v6.16

Toggle pin-init-v6.16's commit message
pin-init changes for v6.16

Added:

- 'Wrapper<T>' trait for creating pin-initializers for wrapper structs
  with a structurally pinned value such as 'UnsafeCell<T>' or
  'MaybeUninit<T>'.

- 'MaybeZeroable' derive macro to try to derive 'Zeroable', but not
  error if not all fields implement it. This is needed to derive
  'Zeroable' for all bindgen-generated structs.

- 'unsafe fn cast_[pin_]init()' functions to unsafely change the
  initialized type of an initializer. These are utilized by the
  'Wrapper<T>' implementations.

Changed:

- Added support for visibility in 'Zeroable' derive macro.

- Added support for 'union's in 'Zeroable' derive macro.

Upstream dev news:

- The CI has been streamlined & some bugs with it have been fixed. I
  also added new workflows to check if the user-space version and the
  one in the kernel tree have diverged.

- I also started to use the issues [1] tab to keep track of any problems
  or unexpected/unwanted things. This should help folks report and
  diagnose issues w.r.t. 'pin-init' better.

[1]: https://github.com/rust-for-linux/pin-init/issues
0