From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: linux-next: Tree for Jun 4 (mm/vmstat.c)
Date: Wed, 4 Jun 2025 12:52:45 +0300 [thread overview]
Message-ID: <zg6ql34habvml3lwr2pq4fl3aibmbf54ezkee5taj2r75qqlbq@x5uqfrveeafl> (raw)
In-Reply-To: <fc028557-648b-4dca-bd46-96cd4d2fbac0@infradead.org>
On Wed, Jun 04, 2025 at 01:16:40AM -0700, Randy Dunlap wrote:
>
>
> On 6/3/25 9:02 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any material destined for v6.17 to you rlinux-next
> > included branches until after v6.16-rc1 has been released.
> >
> > Changes since 20250603:
> >
>
> on x86_64:
>
> ../mm/vmstat.c: In function 'vmstat_start':
> ./../include/linux/compiler_types.h:568:45: error: call to '__compiletime_assert_436' declared with attribute error: BUILD_BUG_ON failed: ARRAY_SIZE(vmstat_text) != NR_VMSTAT_ITEMS
> 568 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> | ^
> ./../include/linux/compiler_types.h:549:25: note: in definition of macro '__compiletime_assert'
> 549 | prefix ## suffix(); \
> | ^~~~~~
> ./../include/linux/compiler_types.h:568:9: note: in expansion of macro '_compiletime_assert'
> 568 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> | ^~~~~~~~~~~~~~~~~~~
> ../include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
> 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
> | ^~~~~~~~~~~~~~~~~~
> ../include/linux/build_bug.h:50:9: note: in expansion of macro 'BUILD_BUG_ON_MSG'
> 50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
> | ^~~~~~~~~~~~~~~~
> ../mm/vmstat.c:1872:9: note: in expansion of macro 'BUILD_BUG_ON'
> 1872 | BUILD_BUG_ON(ARRAY_SIZE(vmstat_text) != NR_VMSTAT_ITEMS);
> | ^~~~~~~~~~~~
>
>
> Full randconfig file is attached.
Thanks for the report!
The fix is here:
https://lore.kernel.org/all/20250604095111.533783-1-kirill.shutemov@linux.intel.com/
--
Kiryl Shutsemau / Kirill A. Shutemov
prev parent reply other threads:[~2025-06-04 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250604140235.2f14220f@canb.auug.org.au>
2025-06-04 8:16 ` Randy Dunlap
2025-06-04 9:52 ` Kirill A. Shutemov [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=zg6ql34habvml3lwr2pq4fl3aibmbf54ezkee5taj2r75qqlbq@x5uqfrveeafl \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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