public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Vlastimil Babka <vbabka@suse•cz>
Cc: 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: Thu, 24 Nov 2022 15:39:23 +1100	[thread overview]
Message-ID: <20221124153923.58a1a9f4@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]

Hi all,

After merging the slab tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

mm/slab_common.c: In function 'kmem_dump_obj':
mm/slab_common.c:603:49: error: 'struct kmem_cache' has no member named 'usersize'
  603 |         if (kp.kp_slab_cache && kp.kp_slab_cache->usersize)
      |                                                 ^~
In file included from include/asm-generic/bug.h:22,
                 from arch/powerpc/include/asm/bug.h:159,
                 from include/linux/bug.h:5,
                 from include/linux/thread_info.h:13,
                 from include/asm-generic/preempt.h:5,
                 from ./arch/powerpc/include/generated/asm/preempt.h:1,
                 from include/linux/preempt.h:78,
                 from include/linux/spinlock.h:56,
                 from include/linux/mmzone.h:8,
                 from include/linux/gfp.h:7,
                 from include/linux/slab.h:15,
                 from mm/slab_common.c:7:
mm/slab_common.c:604:53: error: 'struct kmem_cache' has no member named 'usersize'
  604 |                 pr_cont(" size %u", kp.kp_slab_cache->usersize);
      |                                                     ^~
include/linux/printk.h:429:33: note: in definition of macro 'printk_index_wrap'
  429 |                 _p_func(_fmt, ##__VA_ARGS__);                           \
      |                                 ^~~~~~~~~~~
include/linux/printk.h:542:9: note: in expansion of macro 'printk'
  542 |         printk(KERN_CONT fmt, ##__VA_ARGS__)
      |         ^~~~~~
mm/slab_common.c:604:17: note: in expansion of macro 'pr_cont'
  604 |                 pr_cont(" size %u", kp.kp_slab_cache->usersize);
      |                 ^~~~~~~

Caused by commit

  3cdb7b6ad16a ("mm, slab: ignore hardened usercopy parameters when disabled")

I have used the slab tree from next-20221123 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-11-24  4:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  4:39 Stephen Rothwell [this message]
2022-11-24  8:56 ` linux-next: build failure after merge of the slab tree Vlastimil Babka
  -- strict thread matches above, loose matches on Subject: below --
2024-05-01  5:28 Stephen Rothwell
2024-05-01 15:31 ` Vlastimil Babka
2022-11-25  1:49 Stephen Rothwell
2022-11-25  7:50 ` 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=20221124153923.58a1a9f4@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=vbabka@suse$(echo .)cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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