From: "Barry K. Nathan" <barryn@pobox.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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.3 0000/1257] 7.3.4-rc1 review
Date: Sun, 8 Nov 2026 15:14:22 -0800 [thread overview]
Message-ID: <e9380707-ba1a-4728-8abb-7b1e0335f3db@pobox.com> (raw)
In-Reply-To: <20261108-rc-reply-02-xfs-sched-ext-7.3.4-rc1@kernel.org>
On 11/8/26 8:44 AM, Sasha Levin wrote:
>>> 7.3.4-rc1, 6.18.63-rc1, and 6.12.117-rc1 are all giving me the same build
>>> error with clang that I previously had with 7.3.2-rc1 and 6.18.61-rc1,
>>> due to the same xfs patch as before ("xfs: cross-reference the primary
>>> superblock"):
>
>> I took 7.3.4-rc1, reverted "sched_ext: Fix the stall watchdog testing
>> and blaming the wrong sched under bypass", and added the fix to
>> initialize error to 0 in xchk_superblock() in fs/xfs/scrub/agheader.c
>> (quoted above).
>
> Thanks for testing. Both problems are now dropped: the sched_ext patch from
> 7.3, and "xfs: cross-reference the primary superblock" from 7.3, 6.18 and 6.12
> (it had come back after the earlier drop).
I took 7.3.3 and applied stable-queue as of commit
39e32a361d2fca269cec12e8669e2bd3b84844d9 ("drop 24 patches based on RC
review feedback"), and retested on 2 of my amd64 systems and my arm64
virtual machine.
It's now building successfully and working well, with no regressions
observed.
Tested-by: Barry K. Nathan <barryn@pobox.com>
--
-Barry K. Nathan <barryn@pobox.com>
next prev parent reply other threads:[~2026-11-08 23:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 13:38 Greg Kroah-Hartman
2026-11-07 14:41 ` Brett A C Sheffield
2026-11-07 15:34 ` Ronald Warsow
2026-11-07 16:49 ` Thorsten Leemhuis
2026-11-07 17:27 ` Peter Schneider
2026-11-08 16:44 ` Sasha Levin
2026-11-07 19:33 ` Markus Reichelt
2026-11-07 23:49 ` Barry K. Nathan
2026-11-08 4:59 ` Barry K. Nathan
2026-11-08 16:44 ` Sasha Levin
2026-11-08 23:14 ` Barry K. Nathan [this message]
2026-11-08 1:30 ` Joungmin Lee
2026-11-08 7:42 ` Takeshi Ogasawara
2026-11-08 15:45 ` Miguel Ojeda
2026-11-08 23:44 ` Justin Forbes
2026-11-09 9:25 ` Ron Economos
2026-11-09 9:51 ` Pavel Machek
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=e9380707-ba1a-4728-8abb-7b1e0335f3db@pobox.com \
--to=barryn@pobox.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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=sashal@kernel.org \
--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®