From: Sudip Mukherjee <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: Re: mainline build failure due to e240e53ae0ab ("mm, slub: add CONFIG_SLUB_TINY")
Date: Tue, 13 Dec 2022 10:39:30 +0000 [thread overview]
Message-ID: <CADVatmM4Xr7gKqkeNX90KjmhB-E6H8rSfsK_E+42wp8OmALbDw@mail.gmail.com> (raw)
In-Reply-To: <Y5hTTGf/RA2kpqOF@debian>
On Tue, 13 Dec 2022 at 10:26, Sudip Mukherjee (Codethink)
<sudipm.mukherjee@gmail.com> wrote:
>
> Hi All,
>
> The latest mainline kernel branch fails to build xtensa allmodconfig
> with gcc-11 with the error:
And, also powerpc allmodconfig with the error:
fs/f2fs/inline.c: In function 'f2fs_move_inline_dirents':
./include/linux/fortify-string.h:59:33: error: '__builtin_memset'
pointer overflow between offset [28, 898293814] and size [-898293787,
-1] [-Werror=array-bounds]
59 | #define __underlying_memset __builtin_memset
| ^
./include/linux/fortify-string.h:337:9: note: in expansion of macro
'__underlying_memset'
337 | __underlying_memset(p, c, __fortify_size);
\
| ^~~~~~~~~~~~~~~~~~~
./include/linux/fortify-string.h:345:25: note: in expansion of macro
'__fortify_memset_chk'
345 | #define memset(p, c, s) __fortify_memset_chk(p, c, s,
\
| ^~~~~~~~~~~~~~~~~~~~
fs/f2fs/inline.c:430:9: note: in expansion of macro 'memset'
430 | memset(dst.bitmap + src.nr_bitmap, 0, dst.nr_bitmap -
src.nr_bitmap);
| ^~~~~~
Note: the powerpc failure is also with gcc-11 only. gcc-12 builds fine.
--
Regards
Sudip
next prev parent reply other threads:[~2022-12-13 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 10:26 mainline build failure due to e240e53ae0ab ("mm, slub: add CONFIG_SLUB_TINY") Sudip Mukherjee (Codethink)
2022-12-13 10:39 ` Sudip Mukherjee [this message]
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=CADVatmM4Xr7gKqkeNX90KjmhB-E6H8rSfsK_E+42wp8OmALbDw@mail.gmail.com \
--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.