From: Nathan Chancellor <nathan@kernel.org>
To: Yury Norov <yury.norov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [akpm-mm:mm-nonmm-unstable 22/23] lib/group_cpus.c:352:16: error: array initializer must be an initializer list
Date: Tue, 16 Jan 2024 15:55:36 -0700 [thread overview]
Message-ID: <20240116225536.GA3108998@dev-arch.thelio-3990X> (raw)
In-Reply-To: <202401140117.pwAcsXAT-lkp@intel.com>
On Sun, Jan 14, 2024 at 01:40:11AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
> head: 3d69c575710800c9a4a58e94c157697310e32027
> commit: a868f9c8816cb72f983d1ff940b0938737fe8ee7 [22/23] lib/group_cpus: fix initialization section in group_cpus_evenly()
> config: i386-randconfig-011-20240113 (https://download.01.org/0day-ci/archive/20240114/202401140117.pwAcsXAT-lkp@intel.com/config)
> compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240114/202401140117.pwAcsXAT-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/202401140117.pwAcsXAT-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> lib/group_cpus.c:352:16: error: array initializer must be an initializer list
> 352 | cpumask_var_t npresmsk __free(free_cpumask_var) = NULL;
> | ^
> 1 error generated.
Not a compiler specific error, as evidenced by the GCC report:
https://lore.kernel.org/202401160231.mSAgDn9b-lkp@intel.com/
Neither configuration has CONFIG_CPUMASK_OFFSTACK, which is not going to
be enabled for most configurations, as it is not user selectable without
CONFIG_DEBUG_PER_CPU_MAPS and there are only a few conditions where it
is force selected. In other words, I suspect this error is going to be
quite widespread if it hits -next. I can still reproduce it at the
current mm-nonmm-unstable, commit 08be2d243fb7 ("lib/sort: Optimize
heapsort with double-pop variation").
Cheers,
Nathan
prev parent reply other threads:[~2024-01-16 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 17:40 kernel test robot
2024-01-16 22:55 ` Nathan Chancellor [this message]
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=20240116225536.GA3108998@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yury.norov@gmail.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