mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Barry K. Nathan" <barryn@pobox.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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: Sat, 7 Nov 2026 20:59:00 -0800	[thread overview]
Message-ID: <f6e0e225-a80e-49ee-9555-be300f169503@pobox.com> (raw)
In-Reply-To: <f65916c7-470b-4f64-84d1-da8cf4c8e7e8@pobox.com>

On 11/7/26 3:49 PM, Barry K. Nathan wrote:
> On 11/7/26 5:38 AM, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 7.3.4 release.
>> There are 1257 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, 09 Nov 2026 13:46:08 +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.3.4-rc1.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.3.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
> 
> 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"):
> 
> fs/xfs/scrub/agheader.c:123:6: error: variable 'error' is used uninitialized
>        whenever 'if' condition is true [-Werror,-Wsometimes-uninitialized]
>    123 |         if (agno == 0)
>        |             ^~~~~~~~~
> fs/xfs/scrub/agheader.c:435:9: note: uninitialized use occurs here
>    435 |         return error;
>        |                ^~~~~
> fs/xfs/scrub/agheader.c:123:2: note: remove the 'if' if its condition is always
>        false
>    123 |         if (agno == 0)
>        |         ^~~~~~~~~~~~~~
>    124 |                 goto out_xref;
>        |                 ~~~~~~~~~~~~~
> fs/xfs/scrub/agheader.c:111:13: note: initialize the variable 'error' to silence
>        this warning
>    111 |         int                     error;
>        |                                      ^
>        |                                       = 0
> 1 error generated.
> make[4]: *** [scripts/Makefile.build:287: fs/xfs/scrub/agheader.o] Error 1
> 
> I sent an email about this earlier today, before the -rc was sent out:
> https://lore.kernel.org/stable/7840e515-e7d5-4ef9-8c1d-6390374a5b33@pobox.com/
> 
> Reverting this patch fixes the build, or the minimal fix I proposed in
> that email also fixes the build:
> 
> --- a/fs/xfs/scrub/agheader.c    2026-11-06 22:42:57.147299404 -0800
> +++ b/fs/xfs/scrub/agheader.c    2026-11-06 22:45:59.898908897 -0800
> @@ -108,7 +108,7 @@ xchk_superblock(
>       xfs_agnumber_t        agno = sc->sm->sm_agno;
>       uint32_t        v2_ok;
>       __be32            features_mask;
> -    int            error;
> +    int            error = 0;
>       __be16            vernum_mask;
> 
>       /*
> 
> So far I've only tried building a minimal test config. Later today or
> tomorrow I'll do testing with my normal configs, but (to make a long
> story short) I will probably experience temporary health problems
> for the next few days, so that will probably slow down my testing.

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).

The resulting kernel is running well on 3 different amd64 systems and
an arm64 virtual machine, with no regressions observed. (This includes
a successful XFS scrub on one of the amd64 systems.)
-- 
-Barry K. Nathan  <barryn@pobox.com>


  reply	other threads:[~2026-11-08  4:59 UTC|newest]

Thread overview: 10+ 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-07 19:33 ` Markus Reichelt
2026-11-07 23:49 ` Barry K. Nathan
2026-11-08  4:59   ` Barry K. Nathan [this message]
2026-11-08  1:30 ` Joungmin Lee
2026-11-08  7:42 ` Takeshi Ogasawara

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=f6e0e225-a80e-49ee-9555-be300f169503@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=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®