Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: stable@vger.kernel.org, jack@suse.com
Subject: Re: backport "udf: Allocate name buffer in directory iterator on heap" to 5.15
Date: Mon, 11 Nov 2024 13:57:56 +0100	[thread overview]
Message-ID: <2024111134-empirical-snowcap-8357@gregkh> (raw)
In-Reply-To: <8e759d2a-423f-4e26-b4c2-098965c50f9e@hauke-m.de>

On Sun, Nov 10, 2024 at 06:36:08PM +0100, Hauke Mehrtens wrote:
> Hi,
> 
> I am running into this compile error in 5.15.171 in OpenWrt on 32 bit
> systems. This problem was introduced with kernel 5.15.169.
> ```
> fs/udf/namei.c: In function 'udf_rename':
> fs/udf/namei.c:878:1: error: the frame size of 1144 bytes is larger than
> 1024 bytes [-Werror=frame-larger-than=]
>   878 | }
>       | ^
> cc1: all warnings being treated as errors
> make[2]: *** [scripts/Makefile.build:289: fs/udf/namei.o] Error 1
> make[1]: *** [scripts/Makefile.build:552: fs/udf] Error 2
> ```
> 
> This is fixed by this upstream commit:
> commit 0aba4860b0d0216a1a300484ff536171894d49d8
> Author: Jan Kara <jack@suse.cz>
> Date:   Tue Dec 20 12:38:45 2022 +0100
> 
>     udf: Allocate name buffer in directory iterator on heap
> 
> 
> Please backport this patch to 5.15 too.
> It was already backported to kernel 6.1.

I tried to take it as-is, but it broek the build.  Can you please submit
a tested version that actually works?

thanks,

greg k-h

  reply	other threads:[~2024-11-11 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 17:36 backport "udf: Allocate name buffer in directory iterator on heap" to 5.15 Hauke Mehrtens
2024-11-11 12:57 ` Greg KH [this message]
2024-11-12 20:03   ` Hauke Mehrtens

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=2024111134-empirical-snowcap-8357@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=hauke@hauke-m.de \
    --cc=jack@suse.com \
    --cc=stable@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