From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
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, achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 6.12 0000/1202] 6.12.97-rc2 review
Date: Fri, 24 Jul 2026 08:19:25 +0200 [thread overview]
Message-ID: <2026072454-vividly-suitor-3eb5@gregkh> (raw)
In-Reply-To: <16237d02-bc2c-4401-a1e5-1d81961a65c9@sirena.org.uk>
On Thu, Jul 23, 2026 at 04:17:55PM +0100, Mark Brown wrote:
> On Wed, Jul 22, 2026 at 04:31:38PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.12.97 release.
> > There are 1202 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.
>
> I'm seeing a regression in the proc read kselftest which bisects to
> "proc: protect ptrace_may_access() with exec_update_lock (part 1)":
>
> # selftests: proc: read
> [ 167.845745] ICMPv6: process `read' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time - use net.ipv6.neigh.default.base_reachable_time_ms instead
> [ 167.914113] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) replay-kernel-logs(R)
> [ 168.019358] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098
>
> ...
>
> [ 168.270588] Call trace:
> [ 168.273035] rwsem_read_trylock+0x30/0xe0
> [ 168.277047] proc_map_files_readdir+0x94/0x3dc
> [ 168.281498] iterate_dir+0x118/0x224
> [ 168.285077] __arm64_sys_getdents64+0x70/0x160
> [ 168.289524] invoke_syscall+0x44/0xe4
>
> Full log:
>
> https://lava.sirena.org.uk/scheduler/job/3014030#L10663
Odd, and this is not regressing in Linus's tree as well? Did we miss
something that is needed here that mainline has?
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-24 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 14:31 Greg Kroah-Hartman
2026-07-22 16:54 ` Brett A C Sheffield
2026-07-22 18:27 ` Pavel Machek
2026-07-22 18:40 ` Florian Fainelli
2026-07-23 8:01 ` Peter Schneider
2026-07-23 8:41 ` Shung-Hsi Yu
2026-07-23 11:24 ` Miguel Ojeda
2026-07-23 15:17 ` Mark Brown
2026-07-24 6:19 ` Greg Kroah-Hartman [this message]
2026-07-24 7:38 ` Thorsten Leemhuis
2026-07-24 12:55 ` Mark Brown
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=2026072454-vividly-suitor-3eb5@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=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
Powered by JetHome