On Mon, Mar 9, 2026 at 1:42 AM kernel test robot <[email protected]> wrote:
>
> Hi Sungwoo,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on axboe/for-next]
> [also build test ERROR on device-mapper-dm/for-next linus/master v6.16-rc1 
> next-20260306]
> [cannot apply to linux-nvme/for-next]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url:    
> https://github.com/intel-lab-lkp/linux/commits/Sungwoo-Kim/blk-mq-nvme-Fix-general-protection-fault-in-nvme_setup_descriptor_pools/20260309-143107
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git 
> for-next
> patch link:    
> https://lore.kernel.org/r/20260309062840.2937858-2-iam%40sung-woo.kim
> patch subject: [PATCH] blk-mq: nvme: Fix general protection fault in 
> nvme_setup_descriptor_pools()
> config: x86_64-rhel-9.4-rust 
> (https://download.01.org/0day-ci/archive/20260309/[email protected]/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 
> 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
> reproduce (this is a W=1 build): 
> (https://download.01.org/0day-ci/archive/20260309/[email protected]/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version 
> of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <[email protected]>
> | Closes: 
> https://lore.kernel.org/oe-kbuild-all/[email protected]/
>
> All errors (new ones prefixed by >>):
>
> >> error[E0308]: mismatched types
>    --> rust/kernel/block/mq/operations.rs:274:28
>    |
>    274 |         init_request: Some(Self::init_request_callback),
>    |                       ---- ^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected fn 
> pointer, found fn item
>    |                       |
>    |                       arguments to this enum variant are incorrect
>    |
>    = note: expected fn pointer `unsafe extern "C" fn(_, _, _, i32) -> _`
>    found fn item `unsafe extern "C" fn(_, _, _, u32) -> _ 
> {block::mq::operations::OperationsVTable::<T>::init_request_callback}`
>    help: the type constructed contains `unsafe extern "C" fn(*mut 
> bindings::blk_mq_tag_set, *mut bindings::request, u32, u32) -> i32 
> {block::mq::operations::OperationsVTable::<T>::init_request_callback}` due to 
> the type of the argument passed

Looks like the type of _numa_node in the signature of
init_request_callback() needs to be updated accordingly from c_uint to
c_int.

Best,
Caleb


>    --> rust/kernel/block/mq/operations.rs:274:23
>    |
>    274 |         init_request: Some(Self::init_request_callback),
>    |                       ^^^^^---------------------------^
>    |                            |
>    |                            this argument influences the type of `Some`
>    note: tuple variant defined here
>    --> 
> /opt/cross/rustc-1.88.0-bindgen-0.72.1/rustup/toolchains/1.88.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/option.rs:597:5
>    |
>    597 |     Some(#[stable(feature = "rust1", since = "1.0.0")] T),
>    |     ^^^^
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>

Reply via email to