public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
	Shengwei Luo <luoshengwei@huawei.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Borislav Petkov <bp@alien8.de>,
	Dan Williams <dan.j.williams@intel.com>,
	Daniel Ferguson <danielf@os.amperecomputing.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	James Morse <james.morse@arm.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Len Brown <lenb@kernel.org>, Shiju Jose <shiju.jose@huawei.com>,
	Shuai Xue <xueshuai@linux.alibaba.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Tony Luck <tony.luck@intel.com>,
	Tyler Baicar <tbaicar@codeaurora.org>,
	Will Deacon <will@kernel.org>, Xie XiuQi <xiexiuqi@huawei.com>,
	linux-acpi@vger.kernel.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jason Tian <jason@os.amperecomputing.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH 2/2] RAS: Report all ARM processor CPER information to userspace
Date: Fri, 28 Jun 2024 13:41:28 +0800	[thread overview]
Message-ID: <202406281339.b9yJADtu-lkp@intel.com> (raw)
In-Reply-To: <eed2c4a4fbbb71226ca1944bc7e319bfa9f8aec0.1719471257.git.mchehab+huawei@kernel.org>

Hi Mauro,

kernel test robot noticed the following build errors:

[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on rafael-pm/bleeding-edge linus/master v6.10-rc5 next-20240627]
[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/Mauro-Carvalho-Chehab/RAS-ACPI-APEI-add-conditional-compilation-to-ARM-error-report-functions/20240627-225843
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link:    https://lore.kernel.org/r/eed2c4a4fbbb71226ca1944bc7e319bfa9f8aec0.1719471257.git.mchehab%2Bhuawei%40kernel.org
patch subject: [PATCH 2/2] RAS: Report all ARM processor CPER information to userspace
config: arm64-randconfig-002-20240628 (https://download.01.org/0day-ci/archive/20240628/202406281339.b9yJADtu-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240628/202406281339.b9yJADtu-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/202406281339.b9yJADtu-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/ras/ras.c: In function 'log_arm_hw_error':
>> drivers/ras/ras.c:73:17: error: assignment to 'u8 *' {aka 'unsigned char *'} from incompatible pointer type 'struct cper_arm_ctx_info *' [-Werror=incompatible-pointer-types]
      73 |         ctx_err = ctx_info;
         |                 ^
   cc1: some warnings being treated as errors


vim +73 drivers/ras/ras.c

    54	
    55	void log_arm_hw_error(struct cper_sec_proc_arm *err, const u8 sev)
    56	{
    57	#if defined(CONFIG_ARM) || defined(CONFIG_ARM64)
    58		struct cper_arm_err_info *err_info;
    59		struct cper_arm_ctx_info *ctx_info;
    60		u8 *ven_err_data;
    61		u32 ctx_len = 0;
    62		int n, sz, cpu;
    63		s32 vsei_len;
    64		u32 pei_len;
    65		u8 *pei_err;
    66		u8 *ctx_err;
    67	
    68		pei_len = sizeof(struct cper_arm_err_info) * err->err_info_num;
    69		pei_err = (u8 *)err + sizeof(struct cper_sec_proc_arm);
    70	
    71		err_info = (struct cper_arm_err_info *)(err + 1);
    72		ctx_info = (struct cper_arm_ctx_info *)(err_info + err->err_info_num);
  > 73		ctx_err = ctx_info;
    74		for (n = 0; n < err->context_info_num; n++) {
    75			sz = sizeof(struct cper_arm_ctx_info) + ctx_info->size;
    76			ctx_info = (struct cper_arm_ctx_info *)((long)ctx_info + sz);
    77			ctx_len += sz;
    78		}
    79	
    80		vsei_len = err->section_length - (sizeof(struct cper_sec_proc_arm) +
    81						  pei_len + ctx_len);
    82		if (vsei_len < 0) {
    83			pr_warn(FW_BUG
    84				"section length: %d\n", err->section_length);
    85			pr_warn(FW_BUG
    86				"section length is too small\n");
    87			pr_warn(FW_BUG
    88				"firmware-generated error record is incorrect\n");
    89			vsei_len = 0;
    90		}
    91		ven_err_data = (u8 *)ctx_info;
    92	
    93		cpu = GET_LOGICAL_INDEX(err->mpidr);
    94		/* when return value is invalid, set cpu index to -1 */
    95		if (cpu < 0)
    96			cpu = -1;
    97	
    98		trace_arm_event(err, pei_err, pei_len, ctx_err, ctx_len,
    99				ven_err_data, (u32)vsei_len, sev, cpu);
   100	#endif
   101	}
   102	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-06-28  5:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  7:01 [PATCH 0/2] Add other fields to ARM trace event Mauro Carvalho Chehab
2024-06-27  7:01 ` [PATCH 1/2] RAS: ACPI: APEI: add conditional compilation to ARM error report functions Mauro Carvalho Chehab
2024-06-27  7:50   ` Borislav Petkov
2024-06-27 10:31     ` Mauro Carvalho Chehab
2024-06-28  4:46   ` kernel test robot
2024-06-28  6:04   ` kernel test robot
2024-06-27  7:01 ` [PATCH 2/2] RAS: Report all ARM processor CPER information to userspace Mauro Carvalho Chehab
2024-06-28  5:41   ` kernel test robot [this message]
2024-06-28  9:52   ` 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=202406281339.b9yJADtu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=danielf@os.amperecomputing.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=james.morse@arm.com \
    --cc=jason@os.amperecomputing.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=luoshengwei@huawei.com \
    --cc=mchehab@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shiju.jose@huawei.com \
    --cc=tbaicar@codeaurora.org \
    --cc=tony.luck@intel.com \
    --cc=will@kernel.org \
    --cc=xiexiuqi@huawei.com \
    --cc=xueshuai@linux.alibaba.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox