From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Chengming Zhou <chengming.zhou@linux.dev>,
Nicolas Bouchinet <nicolas.bouchinet@ssi.gouv.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the slab tree
Date: Wed, 1 May 2024 15:28:46 +1000 [thread overview]
Message-ID: <20240501152846.311be492@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Hi all,
After merging the slab tree, today's linux-next build (x86_64
allmodconfig) failed like this:
mm/slub.c: In function 'slab_free_hook':
mm/slub.c:2187:25: error: implicit declaration of function 'get_info_end' [-Werror=implicit-function-declaration]
2187 | inuse = get_info_end(s);
| ^~~~~~~~~~~~
mm/slub.c: In function 'maybe_wipe_obj_freeptr':
mm/slub.c:3872:14: error: implicit declaration of function 'freeptr_outside_object' [-Werror=implicit-function-declaration]
3872 | !freeptr_outside_object(s))
| ^~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Caused by commit
7f39e23ed8dd ("mm/slub: avoid zeroing outside-object freepointer for single free")
$ grep CONFIG_SLUB_DEBUG .config
$
I have used the slab tree from next-20240430 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-05-01 5:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 5:28 Stephen Rothwell [this message]
2024-05-01 15:31 ` linux-next: build failure after merge of the slab tree Vlastimil Babka
-- strict thread matches above, loose matches on Subject: below --
2022-11-25 1:49 Stephen Rothwell
2022-11-25 7:50 ` Vlastimil Babka
2022-11-24 4:39 Stephen Rothwell
2022-11-24 8:56 ` Vlastimil Babka
2022-09-06 6:51 Stephen Rothwell
2022-09-06 7:53 ` Vlastimil Babka
2022-09-06 18:37 ` Alexei Starovoitov
2022-09-07 3:05 ` Alexei Starovoitov
2022-09-07 6:40 ` Vlastimil Babka
2022-09-07 7:45 ` Stephen Rothwell
2013-07-10 2:56 Stephen Rothwell
2013-07-10 7:00 ` Pekka Enberg
2013-07-10 18:48 ` Christoph Lameter
2013-07-11 6:42 ` Pekka Enberg
2011-01-31 3:42 Stephen Rothwell
2011-01-31 19:32 ` Pekka Enberg
2011-02-03 15:19 ` Christoph Lameter
2011-02-08 15:53 ` Christoph Lameter
2011-02-08 15:55 ` Christoph Lameter
2011-02-08 16:50 ` Ted Ts'o
2011-02-08 17:11 ` Sedat Dilek
2011-02-08 17:44 ` Christoph Lameter
2010-12-09 3:03 Stephen Rothwell
2010-12-09 16:25 ` Pekka Enberg
2010-10-27 0:33 Stephen Rothwell
2010-10-27 7:29 ` Pekka Enberg
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=20240501152846.311be492@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chengming.zhou@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicolas.bouchinet@ssi.gouv.fr \
--cc=vbabka@suse.cz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).