From: Lee Jones <lee@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Tom Rix" <trix@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH v5.15 1/1] Kconfig.debug: provide a little extra FRAME_WARN leeway when KASAN is enabled
Date: Tue, 6 Dec 2022 16:13:50 +0000 [thread overview]
Message-ID: <Y49qPgCQ+7iro+ev@google.com> (raw)
In-Reply-To: <Y49mxp1zIyrTlccF@kroah.com>
On Tue, 06 Dec 2022, Greg KH wrote:
> On Tue, Dec 06, 2022 at 02:00:56PM +0000, Lee Jones wrote:
> > On Tue, 06 Dec 2022, Greg KH wrote:
> >
> > > On Tue, Dec 06, 2022 at 12:42:23PM +0000, Lee Jones wrote:
> > > > commit 152fe65f300e1819d59b80477d3e0999b4d5d7d2 upstream.
> > > >
> > > > When enabled, KASAN enlarges function's stack-frames. Pushing quite a few
> > > > over the current threshold. This can mainly be seen on 32-bit
> > > > architectures where the present limit (when !GCC) is a lowly 1024-Bytes.
> > > >
> > > > Link: https://lkml.kernel.org/r/20221125120750.3537134-3-lee@kernel.org
> > > > Signed-off-by: Lee Jones <lee@kernel.org>
> > > > Acked-by: Arnd Bergmann <arnd@arndb.de>
> > > > Cc: Alex Deucher <alexander.deucher@amd.com>
> > > > Cc: "Christian König" <christian.koenig@amd.com>
> > > > Cc: Daniel Vetter <daniel@ffwll.ch>
> > > > Cc: David Airlie <airlied@gmail.com>
> > > > Cc: Harry Wentland <harry.wentland@amd.com>
> > > > Cc: Leo Li <sunpeng.li@amd.com>
> > > > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > > > Cc: Maxime Ripard <mripard@kernel.org>
> > > > Cc: Nathan Chancellor <nathan@kernel.org>
> > > > Cc: Nick Desaulniers <ndesaulniers@google.com>
> > > > Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>
> > > > Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> > > > Cc: Thomas Zimmermann <tzimmermann@suse.de>
> > > > Cc: Tom Rix <trix@redhat.com>
> > > > Cc: <stable@vger.kernel.org>
> > > > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > > > [Lee: Back-ported to linux-5.15.y]
> > > > Signed-off-by: Lee Jones <lee@kernel.org>
> > >
> > > This is already in the -rc1 releases of 5.15 (and 5.10) that went out
> > > yesterday, right?
> > >
> > > Or is that version not correct somehow?
> >
> > Did you fix the back-port already? I was working on the back of:
> >
> > FAILED: patch "[PATCH] Kconfig.debug: provide a little extra FRAME_WARN leeway when" failed to apply to 5.10-stable tree
> > FAILED: patch "[PATCH] Kconfig.debug: provide a little extra FRAME_WARN leeway when" failed to apply to 5.15-stable tree
>
> Sasha seems to have already fixed it, look at the -rc releases for the
> backports.
Works for me. Thank you Sasha.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2022-12-06 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 12:42 [PATCH v5.15 1/1] Kconfig.debug: provide a little extra FRAME_WARN leeway when KASAN is enabled Lee Jones
2022-12-06 12:50 ` Greg KH
2022-12-06 14:00 ` Lee Jones
2022-12-06 15:59 ` Greg KH
2022-12-06 16:13 ` Lee Jones [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=Y49qPgCQ+7iro+ev@google.com \
--to=lee@kernel.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=arnd@arndb.de \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=harry.wentland@amd.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=stable@vger.kernel.org \
--cc=sunpeng.li@amd.com \
--cc=trix@redhat.com \
--cc=tzimmermann@suse.de \
/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