From: Andrew Morton <akpm@linux-foundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Ilya Leoshkevich <iii@linux.ibm.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Anders Roxell <anders.roxell@linaro.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: mm/slub.c:1163:17: error: implicit declaration of function '__memset'; did you mean '__memset64'? [-Werror=implicit-function-declaration]
Date: Tue, 18 Jun 2024 11:42:56 -0700 [thread overview]
Message-ID: <20240618114256.81b30ab4e6de18acd4903c9b@linux-foundation.org> (raw)
In-Reply-To: <CA+G9fYvULzMHHQo3OKkcFYU+Tiw1fFU6LKbt3zHfX-E-ozcsdA@mail.gmail.com>
On Tue, 18 Jun 2024 16:09:38 +0530 Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> The Following build failures have been noticed on Powerpc, mips and arc on the
> Linux next-20240617 tag.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Regressions found on mips:
> - gcc-12-bcm47xx_defconfig
> - gcc-12-cavium_octeon_defconfig
> - gcc-8-malta_defconfig
> - gcc-12-malta_defconfig
> - gcc-12-allnoconfig
> - gcc-8-bcm47xx_defconfig
> - gcc-8-allnoconfig
> - gcc-8-cavium_octeon_defconfig
> - clang-18-allnoconfig
> - clang-nightly-allnoconfig
>
>
> Regressions found on arc:
> - gcc-9-allnoconfig
> - gcc-9-defconfig
>
> Regressions found on powerpc:
> - clang-18-maple_defconfig
> - gcc-13-ppc6xx_defconfig
> - clang-18-allnoconfig
> - clang-18-defconfig
> - clang-18-ppc64e_defconfig
> - gcc-13-defconfig
>
> Build log:
> --------
> mm/slub.c: In function 'init_object':
> mm/slub.c:1163:17: error: implicit declaration of function '__memset';
> did you mean '__memset64'? [-Werror=implicit-function-declaration]
> 1163 | __memset(p - s->red_left_pad, val, s->red_left_pad);
> | ^~~~~~~~
> | __memset64
>
> The commit id:
> ad5dde7da5f9 kmsan: support SLAB_POISON
Thanks. I was hoping for at least a temporary workaround for this, but
nothing is happening. I'll disable that patch for now.
prev parent reply other threads:[~2024-06-18 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 10:39 Naresh Kamboju
2024-06-18 18:42 ` Andrew Morton [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=20240618114256.81b30ab4e6de18acd4903c9b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=cl@linux.com \
--cc=dan.carpenter@linaro.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=penberg@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rientjes@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox