mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ron Economos <re@w6rz.net>
Cc: 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@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com
Subject: Re: [PATCH 7.2 000/243] 7.2.13-rc2 review
Date: Sun, 25 Oct 2026 13:58:24 +0100	[thread overview]
Message-ID: <2026102514-mantra-hypocrite-3567@gregkh> (raw)
In-Reply-To: <567fa279-bdf9-4634-8b4d-ec64c627ebb7@w6rz.net>

On Sun, Oct 25, 2026 at 05:12:48AM -0700, Ron Economos wrote:
> On 10/23/26 23:59, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 7.2.13 release.
> > There are 243 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Mon, 26 Oct 2026 06:46:54 +0000.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 	https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.2.13-rc2.gz
> > or in the git tree and branch at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-7.2.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> Upon further inspection, I've found a dmesg regression:
> 
> Oct 25 04:01:40 riscv64 kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
> 
> Unfortunately, the bisect fails to boot on the very last step. But it's
> either commit "fs: stop sharing fs_struct between init_task and pid 1" or
> commit "fs: add umh argument to struct kernel_clone_args".
> 
> Note that in the commit message of "fs: let idle threads share init_fs" it
> states "Note that kernels before 7.3 need a different backport.". I'm
> guessing all the fs: patches from Christian Brauner should be dropped.
> 
> git bisect start
> # status: waiting for both good and bad commits
> # bad: [7694d244b4f8a6e187060f1f66cc734f5ed16d7b] Linux 7.2.13-rc2
> git bisect bad 7694d244b4f8a6e187060f1f66cc734f5ed16d7b
> # status: waiting for good commit(s), bad commit known
> # good: [cc9de5d4b5ab6459f5774946aa3195ad51236fa8] Linux 7.2.12
> git bisect good cc9de5d4b5ab6459f5774946aa3195ad51236fa8
> # bad: [fa9a1ea1fe845ef8d55048bec58f0c1914f98190] lib/crypto: arm64: Fix lost Poly1305 carry when resuming NEON state
> git bisect bad fa9a1ea1fe845ef8d55048bec58f0c1914f98190
> # good: [8e0e8f6a2381e3a945953f522af34add71424c89] fs: notice when init abandons fs sharing
> git bisect good 8e0e8f6a2381e3a945953f522af34add71424c89
> # bad: [77d6387712803b293c9735c1511a70d38d746590] ring-buffer: Use subbuf_order in available memory estimation
> git bisect bad 77d6387712803b293c9735c1511a70d38d746590
> # bad: [25afd3de9842d1c1f2c443fb673bf9dabd2e5ea3] net: hisilicon: hisi_femac: Move setting of netops to fix crash
> git bisect bad 25afd3de9842d1c1f2c443fb673bf9dabd2e5ea3
> # bad: [fc4fb8a05292c20b1f7cdc310e10dad30da3ccdc] fs: let idle threads share init_fs
> git bisect bad fc4fb8a05292c20b1f7cdc310e10dad30da3ccdc
> # good: [7af0a9a193154ea8818b1d46930646d94818fbc2] fs: make userspace_init_fs a dynamically-initialized pointer
> git bisect good 7af0a9a193154ea8818b1d46930646d94818fbc2
> # bad: [14ec8230d78887f5018867013520f05e212aa701] fs: stop sharing fs_struct between init_task and pid 1
> git bisect bad 14ec8230d78887f5018867013520f05e212aa701
> 

Thanks, will push out a -rc3 soon with these dropped.

greg k-h

  reply	other threads:[~2026-10-25 12:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  6:59 Greg Kroah-Hartman
2026-10-24 10:58 ` Brett A C Sheffield
2026-10-24 14:10 ` Miguel Ojeda
2026-10-24 14:32 ` Barry K. Nathan
2026-10-24 18:08   ` Barry K. Nathan
2026-10-25 12:58     ` Greg Kroah-Hartman
2026-10-24 16:01 ` Markus Reichelt
2026-10-24 20:16 ` Peter Schneider
2026-10-24 20:30 ` Justin Forbes
2026-10-24 21:10 ` SJ Park
2026-10-24 21:17 ` Pavel Machek
2026-10-25  0:30 ` Ron Economos
2026-10-25 10:36 ` Takeshi Ogasawara
2026-10-25 12:12 ` Ron Economos
2026-10-25 12:58   ` Greg Kroah-Hartman [this message]
2026-10-25 12:35 ` Benjamin Boortz
2026-10-25 12:58   ` 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=2026102514-mantra-hypocrite-3567@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --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@nabladev.com \
    --cc=re@w6rz.net \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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®