From: Andrew Morton <akpm@linux-foundation.org>
To: nanook@eskimo.com
Cc: bugzilla-daemon@kernel.org,
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>,
kasan-dev@googlegroups.com, linux-mm@kvack.org
Subject: Re: [Bug 216905] New: Kernel won't compile with KASAN
Date: Mon, 9 Jan 2023 16:09:29 -0800 [thread overview]
Message-ID: <20230109160929.1ecacff5fb8ca2b1ae25141f@linux-foundation.org> (raw)
In-Reply-To: <bug-216905-27@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 09 Jan 2023 23:42:40 +0000 bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216905
>
> Bug ID: 216905
> Summary: Kernel won't compile with KASAN
> Product: Memory Management
> Version: 2.5
> Kernel Version: 6.1.4
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> Assignee: akpm@linux-foundation.org
> Reporter: nanook@eskimo.com
> Regression: No
>
> Created attachment 303563
> --> https://bugzilla.kernel.org/attachment.cgi?id=303563&action=edit
> These are errors when trying to compile KASAN inline
>
> Using GCC 12.2, can not compile a kernel with KASAN enabled, either inline or
> outline.
> The hardware is an i7-6700k based home brew machine, Asus motherboard.
> running Ubuntu 22.10 32GB of RAM but using gcc 12.2 rather than the Ubuntu
> compiler.
crypto/ecc.c: In function ‘ecc_point_mult_shamir’:
crypto/ecc.c:1414:1: warning: the frame size of 1168 bytes is larger than 1024 bytes [-Wframe-larger-than=]
1414 | }
| ^
lib/crypto/curve25519-hacl64.c: In function ‘ladder_cmult.constprop’:
lib/crypto/curve25519-hacl64.c:601:1: warning: the frame size of 1376 bytes is larger than 1024 bytes [-Wframe-larger-than=]
601 | }
| ^
lib/zstd/common/entropy_common.c: In function ‘HUF_readStats’:
lib/zstd/common/entropy_common.c:258:1: warning: the frame size of 1088 bytes is larger than 1024 bytes [-Wframe-larger-than=]
258 | }
| ^
(etcetera)
Increasing CONFIG_FRAME_WARN should fix this. Try 2048.
Perhaps KASAN could increase it somehow to prevent others from tripping
over this.
next parent reply other threads:[~2023-01-10 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216905-27@https.bugzilla.kernel.org/>
2023-01-10 0:09 ` Andrew Morton [this message]
2023-01-10 4:58 ` Robert Dinse
2023-01-10 19:33 ` Theodore Ts'o
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=20230109160929.1ecacff5fb8ca2b1ae25141f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bugzilla-daemon@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=nanook@eskimo.com \
--cc=ryabinin.a.a@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox