From: "Arnd Bergmann" <arnd@arndb.de>
To: "David Laight" <david.laight.linux@gmail.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>,
"Christian Brauner" <brauner@kernel.org>,
"Jan Kara" <jack@suse.cz>, avivdaum <aviv.daum@gmail.com>,
"Adi Nata" <adinata.softwareengineer@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fat: avoid stack overflow warning
Date: Thu, 21 May 2026 16:20:31 +0200 [thread overview]
Message-ID: <8bc8badb-7be9-4445-be5e-1fe80cf628b1@app.fastmail.com> (raw)
In-Reply-To: <20260521133605.56d09a61@pumpkin>
On Thu, May 21, 2026, at 14:36, David Laight wrote:
> On Fri, 15 May 2026 22:44:46 +0200
> Arnd Bergmann <arnd@kernel.org> wrote:
>
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> Building the fat kunit tests on with -fsanitize=alignment
>> reveals some rather excessive stack usage:
>
> What on earth is -fsanitize=alignment doing here?
> (Or even what do it do in general!)
The idea is that the compiler adds sanity checks on accesses
to variables that may be misaligned and print a runtime
warning if this actually happens, see lib/ubsan.c.
As I understand it, the increased stack usage is an
unintended side-effect here, which is the result of
skipping some of the default optimization steps or
being less aggressive about function inlining.
Arnd
next prev parent reply other threads:[~2026-05-21 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 20:44 Arnd Bergmann
2026-05-21 11:41 ` Christian Brauner
2026-05-21 12:03 ` Arnd Bergmann
2026-05-21 12:36 ` David Laight
2026-05-21 14:20 ` Arnd Bergmann [this message]
2026-06-03 6:16 ` OGAWA Hirofumi
2026-06-03 10:06 ` David Laight
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=8bc8badb-7be9-4445-be5e-1fe80cf628b1@app.fastmail.com \
--to=arnd@arndb.de \
--cc=adinata.softwareengineer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=aviv.daum@gmail.com \
--cc=brauner@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®