From: kernel test robot <lkp@intel.com>
To: Qingsong Chen <changxian.cqs@antgroup.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 4/8] rust: kernel: add some info handler TargetOperations
Date: Mon, 26 Jun 2023 00:58:40 +0800 [thread overview]
Message-ID: <202306260042.e8UKaBKy-lkp@intel.com> (raw)
In-Reply-To: <20230625121657.3631109-5-changxian.cqs@antgroup.com>
Hi Qingsong,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on rust/rust-next]
[also build test ERROR on linus/master v6.4-rc7 next-20230623]
[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/Qingsong-Chen/rust-kernel-add-basic-abstractions-for-device-mapper/20230625-201850
base: https://github.com/Rust-for-Linux/linux rust-next
patch link: https://lore.kernel.org/r/20230625121657.3631109-5-changxian.cqs%40antgroup.com
patch subject: [RFC PATCH 4/8] rust: kernel: add some info handler TargetOperations
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230626/202306260042.e8UKaBKy-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230626/202306260042.e8UKaBKy-lkp@intel.com/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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306260042.e8UKaBKy-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0308]: mismatched types
--> rust/kernel/device_mapper.rs:145:34
|
145 | (*$tt).$filed = Some(TargetType::$func::<T>);
| ---- ^^^^^^^^^^^^^^^^^^^^^^ incorrect number of function parameters
| |
| arguments to this enum variant are incorrect
...
170 | / check_target_operations!(
171 | | tt,
172 | | (HAS_CTR, ctr, dm_ctr_fn),
173 | | (HAS_DTR, dtr, dm_dtr_fn),
... |
195 | | (HAS_REPORT_ZONES, report_zones, dm_report_zones_fn),
196 | | );
| |_________________- in this macro invocation
|
= note: expected fn pointer `unsafe extern "C" fn(*mut dm_target) -> _`
found fn item `unsafe extern "C" fn(*mut dm_target, *mut dm_report_zones_args, u32) -> _ {TargetType::dm_report_zones_fn::<T>}`
help: the type constructed contains `unsafe extern "C" fn(*mut dm_target, *mut dm_report_zones_args, u32) -> i32 {TargetType::dm_report_zones_fn::<T>}` due to the type of the argument passed
--> rust/kernel/device_mapper.rs:145:29
|
145 | (*$tt).$filed = Some(TargetType::$func::<T>);
| ^^^^^----------------------^
| |
| this argument influences the type of `Some`
...
170 | / check_target_operations!(
171 | | tt,
172 | | (HAS_CTR, ctr, dm_ctr_fn),
173 | | (HAS_DTR, dtr, dm_dtr_fn),
... |
195 | | (HAS_REPORT_ZONES, report_zones, dm_report_zones_fn),
196 | | );
| |_________________- in this macro invocation
note: tuple variant defined here
--> /opt/cross/rustc-1.68.2-bindgen-0.56.0/rustup/toolchains/1.68.2-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/option.rs:570:5
|
570 | Some(#[stable(feature = "rust1", since = "1.0.0")] T),
| ^^^^
= note: this error originates in the macro `check_target_operations` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0609]: no field `next_sector` on type `dm_report_zones_args`
--> rust/kernel/device_mapper.rs:657:34
|
657 | unsafe { (*self.0.get()).next_sector as _ }
| ^^^^^^^^^^^ unknown field
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-25 16:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 12:16 [RFC PATCH 0/8] Rust device mapper abstractions Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 1/8] rust: kernel: add basic abstractions for device-mapper Qingsong Chen
2023-06-25 12:25 ` Greg KH
2023-06-26 3:26 ` Qingsong Chen
2023-06-26 16:39 ` Boqun Feng
2023-07-14 15:48 ` Benno Lossin
2023-07-17 3:04 ` Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 2/8] rust: kernel: add `request` related TargetOperations Qingsong Chen
2023-07-14 15:49 ` Benno Lossin
2023-07-17 3:42 ` Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 3/8] rust: kernel: add some hook TargetOperations Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 4/8] rust: kernel: add some info handler TargetOperations Qingsong Chen
2023-06-25 16:58 ` kernel test robot [this message]
2023-06-25 12:16 ` [RFC PATCH 5/8] rust: kernel: add underlying device related TargetOperations Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 6/8] rust: kernel: add DAX " Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 7/8] rust: kernel: prepare to implement dm target in Rust Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 8/8] samples: rust: add a device mapper linear target Qingsong Chen
2023-06-30 7:15 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2023-06-25 17:19 [RFC PATCH 4/8] rust: kernel: add some info handler TargetOperations kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202306260042.e8UKaBKy-lkp@intel.com \
--to=lkp@intel.com \
--cc=changxian.cqs@antgroup.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.