From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pascal Ernster <git@hardfalcon.net>
Cc: Ronald Warsow <rwarsow@gmx.de>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.15 000/780] 6.15.3-rc1 review
Date: Sun, 22 Jun 2025 09:24:32 +0200 [thread overview]
Message-ID: <2025062220-appeasing-underling-664c@gregkh> (raw)
In-Reply-To: <79673bf1-1ee7-4c42-8134-ca6ead0a36ac@hardfalcon.net>
On Sun, Jun 22, 2025 at 12:09:42AM +0200, Pascal Ernster wrote:
> [2025-06-19 06:17] Greg Kroah-Hartman:
> > On Wed, Jun 18, 2025 at 10:31:43PM +0200, Pascal Ernster wrote:
> > > Hello again,
> > >
> > >
> > > I've sent this email a few minutes ago but mixed up one of the In-Reply-To
> > > message IDs, so I'm resending it now with (hopefully) the correct
> > > In-Reply-To message IDs.
> > >
> > >
> > > I've bisected this and found that the issue is caused by commit
> > > f46262bbc05af38565c560fd960b86a0e195fd4b:
> > >
> > > 'Revert "mm/execmem: Unify early execmem_cache behaviour"'
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=f46262bbc05af38565c560fd960b86a0e195fd4b
> > >
> > > https://lore.kernel.org/stable/20250617152521.879529420@linuxfoundation.org/
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-6.15/revert-mm-execmem-unify-early-execmem_cache-behaviour.patch?id=344d39fc8d8b7515b45a3bf568c115da12517b22
> >
> > Thank you for digging into this. Looks like I took the last patch in a
> > patch series and not the previous ones, which caused this problem. I've
> > dropped this one now and will add it back next week after I also add all
> > the other ones in the series.
>
>
> You're welcome! :)
>
> Btw, the same patch has turned up again in the stable queue für 6.15.4:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/log/queue-6.15/revert-mm-execmem-unify-early-execmem_cache-behaviour.patch
>
> Is this intentional or a mistake?
Intentional, I took the whole series this time, right?
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-22 7:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:15 Greg Kroah-Hartman
2025-06-17 15:22 ` [PATCH 6.15 468/780] perf symbol: Fix use-after-free in filename__read_build_id Greg Kroah-Hartman
2025-06-17 16:12 ` [PATCH 6.15 000/780] 6.15.3-rc1 review Christian Heusel
2025-06-17 16:49 ` Florian Fainelli
2025-06-17 18:27 ` Ronald Warsow
2025-06-17 21:10 ` Luna Jernberg
2025-06-18 5:42 ` Greg Kroah-Hartman
2025-06-18 13:32 ` Pascal Ernster
[not found] ` <20250617152521.879529420@linuxfoundation.org>
[not found] ` <04b7faf5-2f69-4d02-9eca-916e4bffcf00@gmx.de>
2025-06-18 19:58 ` Pascal Ernster
2025-06-18 20:31 ` Pascal Ernster
2025-06-19 4:17 ` Greg Kroah-Hartman
2025-06-21 22:09 ` Pascal Ernster
2025-06-22 7:24 ` Greg Kroah-Hartman [this message]
2025-06-17 21:17 ` Shuah Khan
2025-06-18 5:51 ` Achill Gilgenast
2025-06-18 6:19 ` Ron Economos
2025-06-18 6:42 ` Jon Hunter
2025-06-18 8:11 ` Takeshi Ogasawara
2025-06-18 8:35 ` Peter Schneider
2025-06-18 10:38 ` Naresh Kamboju
2025-06-18 11:58 ` Mark Brown
2025-06-18 13:19 ` Greg Kroah-Hartman
2025-06-18 14:15 ` Thomas Weißschuh
2025-06-19 4:19 ` Greg Kroah-Hartman
2025-06-19 5:50 ` Thomas Weißschuh
2025-06-19 8:20 ` Greg Kroah-Hartman
2025-06-18 12:59 ` Miguel Ojeda
2025-06-18 18:07 ` Hardik Garg
2025-06-19 1:36 ` Justin Forbes
2025-06-19 4:05 ` Greg Kroah-Hartman
2025-06-19 4:06 ` Greg Kroah-Hartman
2025-06-23 21:05 ` Naresh Kamboju
2025-06-24 10:15 ` Greg Kroah-Hartman
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=2025062220-appeasing-underling-664c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=git@hardfalcon.net \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=rwarsow@gmx.de \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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®