From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Johannes Berg <johannes.berg@intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] wifi: iwlegacy: work around excessive stack usage on clang/kasan
Date: Mon, 23 Jun 2025 12:40:43 +0200 [thread overview]
Message-ID: <20250623104043.GA2260@wp.pl> (raw)
In-Reply-To: <20250620113946.3987160-1-arnd@kernel.org>
On Fri, Jun 20, 2025 at 01:39:42PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> In some rare randconfig builds, I seem to trigger a bug in clang where
> it unrolls a loop but then runs out of registers, which then get
> spilled to the stack:
>
> net/wireless/intel/iwlegacy/4965-rs.c:2262:1: error: stack frame size (1696) exceeds limit (1280) in 'il4965_rs_rate_init' [-Werror,-Wframe-larger-than]
>
> This seems to be the same one I saw in the omapdrm driver, and there is
> an easy workaround by not inlining the il4965_rs_rate_scale_clear_win
> function.
>
> Link: https://github.com/llvm/llvm-project/issues/143908
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Stanislaw Gruszka <stf_xl@wp.pl>
> ---
> drivers/net/wireless/intel/iwlegacy/4965-rs.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/intel/iwlegacy/4965-rs.c b/drivers/net/wireless/intel/iwlegacy/4965-rs.c
> index 0e5130d1fccd..031d88bf6393 100644
> --- a/drivers/net/wireless/intel/iwlegacy/4965-rs.c
> +++ b/drivers/net/wireless/intel/iwlegacy/4965-rs.c
> @@ -203,7 +203,8 @@ il4965_rs_extract_rate(u32 rate_n_flags)
> return (u8) (rate_n_flags & 0xFF);
> }
>
> -static void
> +/* noinline works around https://github.com/llvm/llvm-project/issues/143908 */
> +static noinline_for_stack void
> il4965_rs_rate_scale_clear_win(struct il_rate_scale_data *win)
> {
> win->data = 0;
> --
> 2.39.5
>
prev parent reply other threads:[~2025-06-23 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 11:39 [PATCH] wifi: iwlegacy: work around excessive stack usage on clang/kasan Arnd Bergmann
2025-06-23 10:40 ` Stanislaw Gruszka [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=20250623104043.GA2260@wp.pl \
--to=stf_xl@wp.pl \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=johannes.berg@intel.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.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