From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9D06B7C; Sun, 25 Jun 2023 16:58:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1687712327; x=1719248327; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=wvYTBAUfqZCX+rchOTcyoZSkQ68pK7tRktmXOWnLbC0=; b=nKaRuXfwyJyhwUnnB2U8EtsCyPN32BBWzk9aUzY/puqWY2XAyKUx2d/n Ht+oit/3HpVa9YH4BlqY0zec4RPuzeHKrgZ9x6+z1+xCilL2LvLo/koR6 ++8N5Errda5nqoBn4k0FraCzDAWZ7iBpztlQkunPxYXUxQar/3cnCcHhn FaPd/pi3NOwu3R43483T4xJ4koSozo8NmTpzOEK79Y+493HgemM4chymf kGECszQXzc7v9yfcMMVRKWKmHVCTrjxpkyDaIPd7lkSZ8xwPoTlabZmn4 usO4257SH0Y/jNjHIQRCMPO0c8RfY1X7TGZNNqV0fMOpNnsRilxQZFKJ2 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10752"; a="341430678" X-IronPort-AV: E=Sophos;i="6.01,157,1684825200"; d="scan'208";a="341430678" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Jun 2023 09:58:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10752"; a="719085642" X-IronPort-AV: E=Sophos;i="6.01,157,1684825200"; d="scan'208";a="719085642" Received: from lkp-server01.sh.intel.com (HELO 783282924a45) ([10.239.97.150]) by fmsmga007.fm.intel.com with ESMTP; 25 Jun 2023 09:58:45 -0700 Received: from kbuild by 783282924a45 with local (Exim 4.96) (envelope-from ) id 1qDT4W-000A8r-2C; Sun, 25 Jun 2023 16:58:44 +0000 Date: Mon, 26 Jun 2023 00:58:40 +0800 From: kernel test robot To: Qingsong Chen Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev Subject: Re: [RFC PATCH 4/8] rust: kernel: add some info handler TargetOperations Message-ID: <202306260042.e8UKaBKy-lkp@intel.com> References: <20230625121657.3631109-5-changxian.cqs@antgroup.com> Precedence: bulk X-Mailing-List: llvm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 | 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::); | ---- ^^^^^^^^^^^^^^^^^^^^^^ 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::}` help: the type constructed contains `unsafe extern "C" fn(*mut dm_target, *mut dm_report_zones_args, u32) -> i32 {TargetType::dm_report_zones_fn::}` due to the type of the argument passed --> rust/kernel/device_mapper.rs:145:29 | 145 | (*$tt).$filed = Some(TargetType::$func::); | ^^^^^----------------------^ | | | 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