All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Alexander Potapenko <glider@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: mainline build failure due to e240e53ae0ab ("mm, slub: add CONFIG_SLUB_TINY")
Date: Tue, 13 Dec 2022 10:26:20 +0000	[thread overview]
Message-ID: <Y5hTTGf/RA2kpqOF@debian> (raw)

Hi All,

The latest mainline kernel branch fails to build xtensa allmodconfig 
with gcc-11 with the error:

kernel/kcsan/kcsan_test.c: In function '__report_matches':
kernel/kcsan/kcsan_test.c:257:1: error: the frame size of 1680 bytes is larger than 1536 bytes [-Werror=frame-larger-than=]
  257 | }
      | ^

git bisect pointed to e240e53ae0ab ("mm, slub: add CONFIG_SLUB_TINY")


I will be happy to test any patch or provide any extra log if needed.

Note:
This is only seen with gcc-11, gcc-12 builds are ok.

-- 
Regards
Sudip


             reply	other threads:[~2022-12-13 10:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 10:26 Sudip Mukherjee (Codethink) [this message]
2022-12-13 10:39 ` mainline build failure due to e240e53ae0ab ("mm, slub: add CONFIG_SLUB_TINY") Sudip Mukherjee
2022-12-13 12:56   ` Guenter Roeck
2022-12-13 13:11 ` Guenter Roeck
2022-12-13 13:27   ` Vlastimil Babka
2022-12-13 14:11     ` Guenter Roeck
2022-12-13 15:21       ` Vlastimil Babka
2022-12-22 12:06 ` mainline build failure due to e240e53ae0ab ("mm, slub: add CONFIG_SLUB_TINY") #forregzbot Thorsten Leemhuis
2023-01-04 13:57   ` Linux kernel regression tracking (#update)

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=Y5hTTGf/RA2kpqOF@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryabinin.a.a@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=vincenzo.frascino@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.