From: David Laight <david.laight.linux@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Arnd Bergmann <arnd@arndb.de>,
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 13:36:05 +0100 [thread overview]
Message-ID: <20260521133605.56d09a61@pumpkin> (raw)
In-Reply-To: <20260515204456.2692208-1-arnd@kernel.org>
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!)
From a 'testing the kernel' point of view I don't think you'd ever
want to copy a structure that might be misaligned.
(Quite how it does that in the general case when the address of something
in the structure might get passed to passed to code that knows the address
by other means is anybodies guess.)
The most you might want for 'kernel hardening' is a software check that
run-time errors misaligned structures.
-- David
>
> fs/fat/fat_test.c: In function 'fat_clus_to_blknr_test':
> fs/fat/fat_test.c:33:1: error: the frame size of 4736 bytes is larger than 1536 bytes [-Werror=frame-larger-than=]
> 33 | }
> | ^
> fs/fat/fat_test.c: In function 'fat_get_blknr_offset_test':
> fs/fat/fat_test.c:52:1: error: the frame size of 4800 bytes is larger than 1536 bytes [-Werror=frame-larger-than=]
>
> The problem is clearly related to the on-stack copy of a local
> msdos_sb_info structure. Avoid this by making that copy
> 'static const' and changing the called functions to accept
> a constant input.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> fs/fat/fat.h | 4 ++--
> fs/fat/fat_test.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/fat/fat.h b/fs/fat/fat.h
> index 5a58f0bf8ce8..52bced59abe4 100644
> --- a/fs/fat/fat.h
> +++ b/fs/fat/fat.h
> @@ -247,13 +247,13 @@ static inline unsigned char fat_checksum(const __u8 *name)
> return s;
> }
>
> -static inline sector_t fat_clus_to_blknr(struct msdos_sb_info *sbi, int clus)
> +static inline sector_t fat_clus_to_blknr(const struct msdos_sb_info *sbi, int clus)
> {
> return ((sector_t)clus - FAT_START_ENT) * sbi->sec_per_clus
> + sbi->data_start;
> }
>
> -static inline void fat_get_blknr_offset(struct msdos_sb_info *sbi,
> +static inline void fat_get_blknr_offset(const struct msdos_sb_info *sbi,
> loff_t i_pos, sector_t *blknr, int *offset)
> {
> *blknr = i_pos >> sbi->dir_per_block_bits;
> diff --git a/fs/fat/fat_test.c b/fs/fat/fat_test.c
> index 4eeed9dca549..9583ce66dca3 100644
> --- a/fs/fat/fat_test.c
> +++ b/fs/fat/fat_test.c
> @@ -22,7 +22,7 @@ static void fat_checksum_test(struct kunit *test)
>
> static void fat_clus_to_blknr_test(struct kunit *test)
> {
> - struct msdos_sb_info sbi = {
> + static const struct msdos_sb_info sbi = {
> .sec_per_clus = 4,
> .data_start = 100,
> };
> @@ -34,7 +34,7 @@ static void fat_clus_to_blknr_test(struct kunit *test)
>
> static void fat_get_blknr_offset_test(struct kunit *test)
> {
> - struct msdos_sb_info sbi = {
> + static const struct msdos_sb_info sbi = {
> .dir_per_block = 16,
> .dir_per_block_bits = 4,
> };
next prev parent reply other threads:[~2026-05-21 12:36 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 [this message]
2026-05-21 14:20 ` Arnd Bergmann
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=20260521133605.56d09a61@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=adinata.softwareengineer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=aviv.daum@gmail.com \
--cc=brauner@kernel.org \
--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
Powered by JetHome