mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, m.wieczorretman@pm.me,
	Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/3] x86/cpu: Check if feature string is non-zero
Date: Sat, 21 Feb 2026 00:19:59 +0800	[thread overview]
Message-ID: <202602210027.MJpPrtwD-lkp@intel.com> (raw)
In-Reply-To: <bc0eebc8310acfae28a73e3780a67d721c739b89.1771590895.git.m.wieczorretman@pm.me>

Hi Maciej,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/x86/core]
[also build test WARNING on tip/smp/core v6.19]
[cannot apply to peterz-queue/sched/core linus/master next-20260219]
[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/Maciej-Wieczor-Retman/x86-cpu-Clear-feature-bits-disabled-at-compile-time/20260220-204916
base:   tip/x86/core
patch link:    https://lore.kernel.org/r/bc0eebc8310acfae28a73e3780a67d721c739b89.1771590895.git.m.wieczorretman%40pm.me
patch subject: [PATCH v6 2/3] x86/cpu: Check if feature string is non-zero
config: x86_64-randconfig-003-20260220 (https://download.01.org/0day-ci/archive/20260221/202602210027.MJpPrtwD-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260221/202602210027.MJpPrtwD-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/202602210027.MJpPrtwD-lkp@intel.com/

All warnings (new ones prefixed by >>):

   arch/x86/kernel/cpu/common.c: In function 'x86_cap_name':
>> arch/x86/kernel/cpu/common.c:1987:29: warning: argument to 'sizeof' in 'snprintf' call is the same expression as the destination; did you mean to provide an explicit length? [-Wsizeof-pointer-memaccess]
    1987 |         snprintf(buf, sizeof(buf), "%u:%u", word, bit & 31);
         |                             ^
>> arch/x86/kernel/cpu/common.c:1987:37: warning: '%u' directive output may be truncated writing between 1 and 9 bytes into a region of size 8 [-Wformat-truncation=]
    1987 |         snprintf(buf, sizeof(buf), "%u:%u", word, bit & 31);
         |                                     ^~
   arch/x86/kernel/cpu/common.c:1987:36: note: directive argument in the range [0, 134217727]
    1987 |         snprintf(buf, sizeof(buf), "%u:%u", word, bit & 31);
         |                                    ^~~~~~~
   arch/x86/kernel/cpu/common.c:1987:36: note: directive argument in the range [0, 31]
   arch/x86/kernel/cpu/common.c:1987:9: note: 'snprintf' output between 4 and 13 bytes into a destination of size 8
    1987 |         snprintf(buf, sizeof(buf), "%u:%u", word, bit & 31);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


vim +1987 arch/x86/kernel/cpu/common.c

  1973	
  1974	const char *x86_cap_name(unsigned int bit, char *buf)
  1975	{
  1976		unsigned int word = bit >> 5;
  1977		const char *name = NULL;
  1978	
  1979		if (likely(word < NCAPINTS))
  1980			name = x86_cap_flags[bit];
  1981		else if (likely(word < NCAPINTS + NBUGINTS))
  1982			name = x86_bug_flags[bit - 32 * NCAPINTS];
  1983	
  1984		if (name)
  1985			return name;
  1986	
> 1987		snprintf(buf, sizeof(buf), "%u:%u", word, bit & 31);
  1988		return buf;
  1989	}
  1990	

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

  reply	other threads:[~2026-02-20 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 12:43 [PATCH v6 0/3] x86: Capability bits fix and required bits sanity check Maciej Wieczor-Retman
2026-02-20 12:44 ` [PATCH v6 1/3] x86/cpu: Clear feature bits disabled at compile-time Maciej Wieczor-Retman
2026-02-20 12:44 ` [PATCH v6 2/3] x86/cpu: Check if feature string is non-zero Maciej Wieczor-Retman
2026-02-20 16:19   ` kernel test robot [this message]
2026-02-20 16:43     ` Maciej Wieczor-Retman
2026-02-20 21:05   ` kernel test robot
2026-02-20 12:44 ` [PATCH v6 3/3] x86/cpu: Do a sanity check on required feature bits Maciej Wieczor-Retman

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=202602210027.MJpPrtwD-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.wieczorretman@pm.me \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    /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

Powered by JetHome