From: Kees Cook <keescook@chromium.org>
To: "kernelci.org bot" <bot@kernelci.org>, Bixuan Cui <cuibixuan@huawei.com>
Cc: linux-next@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
tglx@linutronix.de
Subject: Re: next/master build: 210 builds: 7 failed, 203 passed, 7 errors, 1669 warnings (next-20210914)
Date: Thu, 16 Sep 2021 09:12:45 -0700 [thread overview]
Message-ID: <202109160900.0E416B0E9@keescook> (raw)
In-Reply-To: <61405e17.1c69fb81.67290.bb2c@mx.google.com>
On Tue, Sep 14, 2021 at 01:32:23AM -0700, kernelci.org bot wrote:
> Errors summary:
>
> 2 include/linux/slab.h:618:9: error: argument 1 value ‘18446744073709551615’ exceeds maximum object size 9223372036854775807 [-Werror=alloc-size-larger-than=]
> 1 include/linux/slab.h:461:9: error: argument 1 value ‘4294967295’ exceeds maximum object size 2147483647 [-Werror=alloc-size-larger-than=]
> 1 drivers/staging/greybus/audio_topology.c:977:12: error: stack frame size of 3312 bytes in function 'gbaudio_tplg_create_widget' [-Werror,-Wframe-larger-than=]
> 1 drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:138:4: error: argument 1 value ‘4294967295’ exceeds maximum object size 2147483647 [-Werror=alloc-size-larger-than=]
These (the same root cause as [1]) are fixed by:
https://lore.kernel.org/lkml/20210910201132.3809437-1-keescook@chromium.org/
which is in mmots (soon to be mmotm, soon to be in -next):
https://www.ozlabs.org/~akpm/mmots/broken-out/compiler-attributes-add-__alloc_size-for-better-bounds-checking-fix.patch
-Kees
[1] https://lore.kernel.org/lkml/20210908014623.61357-1-cuibixuan@huawei.com/
--
Kees Cook
prev parent reply other threads:[~2021-09-16 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 8:32 next/master build: 210 builds: 7 failed, 203 passed, 7 errors, 1669 warnings (next-20210914) kernelci.org bot
2021-09-16 16:12 ` Kees Cook [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=202109160900.0E416B0E9@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bot@kernelci.org \
--cc=cuibixuan@huawei.com \
--cc=linux-next@vger.kernel.org \
--cc=tglx@linutronix.de \
/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