mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryan Roberts <ryan.roberts@arm.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.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@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH 6.12 000/150] 6.12.18-rc1 review
Date: Thu, 6 Mar 2025 13:01:33 +0000	[thread overview]
Message-ID: <a20a3f80-9253-4c71-8533-7afb129678f9@arm.com> (raw)
In-Reply-To: <CA+G9fYvwoYVG8wgz6Lu68EO1z3m4mbBWroGEXL2w5D7P_4SG-g@mail.gmail.com>

On 06/03/2025 12:11, Naresh Kamboju wrote:
> On Wed, 5 Mar 2025 at 23:35, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> This is the start of the stable review cycle for the 6.12.18 release.
>> There are 150 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 Fri, 07 Mar 2025 17:44:26 +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/v6.x/stable-review/patch-6.12.18-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-6.12.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
> 
> Regressions on arm64 the defconfig builds failed with clang-20 and gcc-13
> the stable-rc 6.12.18-rc1 and 6.13.6-rc1.
> 
> First seen on the 6.12.18-rc1
>  Good: v6.12.14
>  Bad: 6.12.18-rc1
> 
> * arm64, build
>   - clang-20-defconfig
>   - clang-nightly-defconfig
>   - gcc-13-defconfig
>   - gcc-8-defconfig
> 
> Regression Analysis:
>  - New regression? yes
>  - Reproducibility? Yes
> 
> This commmit is causing build regressions,
>   arm64: hugetlb: Fix huge_ptep_get_and_clear() for non-present ptes
>   commit 49c87f7677746f3c5bd16c81b23700bb6b88bfd4 upstream.
> 
> Build regression: arm64 hugetlbpage.c undeclared identifier 'sz'
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> ## Build log
> arch/arm64/mm/hugetlbpage.c:386:28: error: use of undeclared identifier 'sz'
>   386 |         ncontig = num_contig_ptes(sz, &pgsize);
>       |                                   ^
> 1 error generated.

This is the same problem we were discussing againt the 6.13 backport. This patch
depends on a patch that conflicted so wasn't auto-backported. I'll send out the
manual backports in due course.

> 
> 
> ## Source
> * Kernel version: 6.12.18-rc1
> * Git tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> * Git sha: 43639cc57b2273fce42874dd7f6e0b872f4984c5
> * Git describe: v6.12.15-531-g43639cc57b22
> * Project details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.12.y/build/v6.12.15-531-g43639cc57b22
> 
> ## Build
> * Build log: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.12.y/build/v6.12.15-531-g43639cc57b22/testrun/27516239/suite/build/test/clang-20-defconfig/log
> * Build history:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.12.y/build/v6.12.15-531-g43639cc57b22/testrun/27514393/suite/build/test/clang-20-defconfig/history/
> * Build details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.12.y/build/v6.12.15-531-g43639cc57b22/testrun/27516239/suite/build/test/clang-20-defconfig/
> * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2tuR9WQOit4WjRC1XVxLJKTcQia/
> * Kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2tuR9WQOit4WjRC1XVxLJKTcQia/config
> 
> ## Steps to reproduce
>  - tuxmake --runtime podman --target-arch arm64 --toolchain clang-20
> --kconfig defconfig LLVM=1 LLVM_IAS=1
> 
> 
> --
> Linaro LKFT
> https://lkft.linaro.org


  reply	other threads:[~2025-03-06 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 17:47 Greg Kroah-Hartman
2025-03-06  1:11 ` SeongJae Park
2025-03-06  2:48 ` Peter Schneider
2025-03-06  8:10 ` Ron Economos
2025-03-06 12:11 ` Naresh Kamboju
2025-03-06 13:01   ` Ryan Roberts [this message]
2025-03-06 12:14 ` Jon Hunter
2025-03-06 15:54 ` Shuah Khan
2025-03-06 16:23 ` Hardik Garg

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=a20a3f80-9253-4c71-8533-7afb129678f9@arm.com \
    --to=ryan.roberts@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.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=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.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®