* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
@ 2023-10-04 19:33 ` Florian Fainelli
2023-10-04 20:19 ` Namhyung Kim
2023-10-05 0:17 ` Wang Yugui
` (10 subsequent siblings)
11 siblings, 1 reply; 25+ messages in thread
From: Florian Fainelli @ 2023-10-04 19:33 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable, Namhyung Kim, Ian Rogers
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, sudipm.mukherjee, srw, rwarsow,
conor
+Namhyung, Ian,
On 10/4/23 10:52, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
perf fails to build with:
fixdep: error opening depfile:
/local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/.pmu-events.o.d:
No such file or directory
make[5]: *** [pmu-events/Build:33:
/local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events.o]
Error 2
make[4]: *** [Makefile.perf:672:
/local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events-in.o]
Error 2
make[3]: *** [Makefile.perf:240: sub-make] Error 2
make[2]: *** [Makefile:70: all] Error 2
make[1]: *** [package/pkg-generic.mk:294:
/local/users/fainelli/buildroot/output/arm/build/linux-tools/.stamp_built]
Error 2
make: *** [Makefile:27: _all] Error 2
due a80fd00cb1a7793ead4d7c3fa7d3f1e898231c27 ("perf build: Update build
rule for generated files"). Reverting that commit fixes the build for me
and then all is good in terms of testing.
--
Florian
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 19:33 ` Florian Fainelli
@ 2023-10-04 20:19 ` Namhyung Kim
2023-10-05 0:51 ` Florian Fainelli
0 siblings, 1 reply; 25+ messages in thread
From: Namhyung Kim @ 2023-10-04 20:19 UTC (permalink / raw)
To: Florian Fainelli
Cc: Greg Kroah-Hartman, stable, Ian Rogers, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, sudipm.mukherjee, srw, rwarsow, conor
Hello,
On Wed, Oct 4, 2023 at 12:33 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>
> +Namhyung, Ian,
>
> On 10/4/23 10:52, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.56 release.
> > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> perf fails to build with:
>
> fixdep: error opening depfile:
> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/.pmu-events.o.d:
> No such file or directory
> make[5]: *** [pmu-events/Build:33:
> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events.o]
> Error 2
> make[4]: *** [Makefile.perf:672:
> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events-in.o]
> Error 2
> make[3]: *** [Makefile.perf:240: sub-make] Error 2
> make[2]: *** [Makefile:70: all] Error 2
> make[1]: *** [package/pkg-generic.mk:294:
> /local/users/fainelli/buildroot/output/arm/build/linux-tools/.stamp_built]
> Error 2
> make: *** [Makefile:27: _all] Error 2
>
> due a80fd00cb1a7793ead4d7c3fa7d3f1e898231c27 ("perf build: Update build
> rule for generated files"). Reverting that commit fixes the build for me
> and then all is good in terms of testing.
I think it's ok to drop the patches if it's not applied
cleanly.
Thanks,
Namhyung
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 20:19 ` Namhyung Kim
@ 2023-10-05 0:51 ` Florian Fainelli
2023-10-05 5:15 ` Namhyung Kim
0 siblings, 1 reply; 25+ messages in thread
From: Florian Fainelli @ 2023-10-05 0:51 UTC (permalink / raw)
To: Namhyung Kim
Cc: Greg Kroah-Hartman, stable, Ian Rogers, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, sudipm.mukherjee, srw, rwarsow, conor
On 10/4/2023 1:19 PM, Namhyung Kim wrote:
> Hello,
>
> On Wed, Oct 4, 2023 at 12:33 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>>
>> +Namhyung, Ian,
>>
>> On 10/4/23 10:52, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 6.1.56 release.
>>> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> perf fails to build with:
>>
>> fixdep: error opening depfile:
>> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/.pmu-events.o.d:
>> No such file or directory
>> make[5]: *** [pmu-events/Build:33:
>> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events.o]
>> Error 2
>> make[4]: *** [Makefile.perf:672:
>> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events-in.o]
>> Error 2
>> make[3]: *** [Makefile.perf:240: sub-make] Error 2
>> make[2]: *** [Makefile:70: all] Error 2
>> make[1]: *** [package/pkg-generic.mk:294:
>> /local/users/fainelli/buildroot/output/arm/build/linux-tools/.stamp_built]
>> Error 2
>> make: *** [Makefile:27: _all] Error 2
>>
>> due a80fd00cb1a7793ead4d7c3fa7d3f1e898231c27 ("perf build: Update build
>> rule for generated files"). Reverting that commit fixes the build for me
>> and then all is good in terms of testing.
>
> I think it's ok to drop the patches if it's not applied
> cleanly.
AFAICT the patch applied cleanly. There was some bizarre interplay in
stable kernels prior to < 6.1 as reported here:
https://lore.kernel.org/all/dcb9997a-2e8a-5eb2-7a34-f8af418d4bf1@gmail.com/
https://lore.kernel.org/all/6a577578-8adb-aa70-1bf8-b1a4573152cf@gmail.com/
Does this make sense to you that on 6.1 which does have Ian's commit
00facc760903be6675870c2749e2cd72140e396e ("perf jevents: Switch build to
use jevents.py") that we would still get this build error somehow?
Thanks
--
Florian
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 0:51 ` Florian Fainelli
@ 2023-10-05 5:15 ` Namhyung Kim
2023-10-06 10:12 ` Greg Kroah-Hartman
0 siblings, 1 reply; 25+ messages in thread
From: Namhyung Kim @ 2023-10-05 5:15 UTC (permalink / raw)
To: Florian Fainelli
Cc: Greg Kroah-Hartman, stable, Ian Rogers, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, sudipm.mukherjee, srw, rwarsow, conor
On Wed, Oct 4, 2023 at 5:52 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>
>
>
> On 10/4/2023 1:19 PM, Namhyung Kim wrote:
> > Hello,
> >
> > On Wed, Oct 4, 2023 at 12:33 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
> >>
> >> +Namhyung, Ian,
> >>
> >> On 10/4/23 10:52, Greg Kroah-Hartman wrote:
> >>> This is the start of the stable review cycle for the 6.1.56 release.
> >>> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> >>> and the diffstat can be found below.
> >>>
> >>> thanks,
> >>>
> >>> greg k-h
> >>
> >> perf fails to build with:
> >>
> >> fixdep: error opening depfile:
> >> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/.pmu-events.o.d:
> >> No such file or directory
> >> make[5]: *** [pmu-events/Build:33:
> >> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events.o]
> >> Error 2
> >> make[4]: *** [Makefile.perf:672:
> >> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events-in.o]
> >> Error 2
> >> make[3]: *** [Makefile.perf:240: sub-make] Error 2
> >> make[2]: *** [Makefile:70: all] Error 2
> >> make[1]: *** [package/pkg-generic.mk:294:
> >> /local/users/fainelli/buildroot/output/arm/build/linux-tools/.stamp_built]
> >> Error 2
> >> make: *** [Makefile:27: _all] Error 2
> >>
> >> due a80fd00cb1a7793ead4d7c3fa7d3f1e898231c27 ("perf build: Update build
> >> rule for generated files"). Reverting that commit fixes the build for me
> >> and then all is good in terms of testing.
> >
> > I think it's ok to drop the patches if it's not applied
> > cleanly.
>
> AFAICT the patch applied cleanly. There was some bizarre interplay in
> stable kernels prior to < 6.1 as reported here:
>
> https://lore.kernel.org/all/dcb9997a-2e8a-5eb2-7a34-f8af418d4bf1@gmail.com/
> https://lore.kernel.org/all/6a577578-8adb-aa70-1bf8-b1a4573152cf@gmail.com/
>
> Does this make sense to you that on 6.1 which does have Ian's commit
> 00facc760903be6675870c2749e2cd72140e396e ("perf jevents: Switch build to
> use jevents.py") that we would still get this build error somehow?
You can drop the pmu-events part of the change if possible.
If not, I'm ok to drop the entire patch as it's intended to fix a
corner case only. Normal builds should be fine before and
after the change.
Thanks,
Namhyung
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 5:15 ` Namhyung Kim
@ 2023-10-06 10:12 ` Greg Kroah-Hartman
0 siblings, 0 replies; 25+ messages in thread
From: Greg Kroah-Hartman @ 2023-10-06 10:12 UTC (permalink / raw)
To: Namhyung Kim
Cc: Florian Fainelli, stable, Ian Rogers, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, sudipm.mukherjee, srw, rwarsow, conor
On Wed, Oct 04, 2023 at 10:15:16PM -0700, Namhyung Kim wrote:
> On Wed, Oct 4, 2023 at 5:52 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
> >
> >
> >
> > On 10/4/2023 1:19 PM, Namhyung Kim wrote:
> > > Hello,
> > >
> > > On Wed, Oct 4, 2023 at 12:33 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
> > >>
> > >> +Namhyung, Ian,
> > >>
> > >> On 10/4/23 10:52, Greg Kroah-Hartman wrote:
> > >>> This is the start of the stable review cycle for the 6.1.56 release.
> > >>> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > >>> and the diffstat can be found below.
> > >>>
> > >>> thanks,
> > >>>
> > >>> greg k-h
> > >>
> > >> perf fails to build with:
> > >>
> > >> fixdep: error opening depfile:
> > >> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/.pmu-events.o.d:
> > >> No such file or directory
> > >> make[5]: *** [pmu-events/Build:33:
> > >> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events.o]
> > >> Error 2
> > >> make[4]: *** [Makefile.perf:672:
> > >> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events-in.o]
> > >> Error 2
> > >> make[3]: *** [Makefile.perf:240: sub-make] Error 2
> > >> make[2]: *** [Makefile:70: all] Error 2
> > >> make[1]: *** [package/pkg-generic.mk:294:
> > >> /local/users/fainelli/buildroot/output/arm/build/linux-tools/.stamp_built]
> > >> Error 2
> > >> make: *** [Makefile:27: _all] Error 2
> > >>
> > >> due a80fd00cb1a7793ead4d7c3fa7d3f1e898231c27 ("perf build: Update build
> > >> rule for generated files"). Reverting that commit fixes the build for me
> > >> and then all is good in terms of testing.
> > >
> > > I think it's ok to drop the patches if it's not applied
> > > cleanly.
> >
> > AFAICT the patch applied cleanly. There was some bizarre interplay in
> > stable kernels prior to < 6.1 as reported here:
> >
> > https://lore.kernel.org/all/dcb9997a-2e8a-5eb2-7a34-f8af418d4bf1@gmail.com/
> > https://lore.kernel.org/all/6a577578-8adb-aa70-1bf8-b1a4573152cf@gmail.com/
> >
> > Does this make sense to you that on 6.1 which does have Ian's commit
> > 00facc760903be6675870c2749e2cd72140e396e ("perf jevents: Switch build to
> > use jevents.py") that we would still get this build error somehow?
>
> You can drop the pmu-events part of the change if possible.
> If not, I'm ok to drop the entire patch as it's intended to fix a
> corner case only. Normal builds should be fine before and
> after the change.
I'm going to just drop the patch now from all queues, thanks!
greg k-h
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
2023-10-04 19:33 ` Florian Fainelli
@ 2023-10-05 0:17 ` Wang Yugui
2023-10-06 10:12 ` Greg Kroah-Hartman
2023-10-05 0:59 ` Shuah Khan
` (9 subsequent siblings)
11 siblings, 1 reply; 25+ messages in thread
From: Wang Yugui @ 2023-10-05 0:17 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor
Hi,
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
This 6.1.56-rc1 failed to build on rhel7 with dev-tool-set 8, but 6.1.55 works.
Build error message:
gcc: fatal error: no input files
make[3]: *** [pmu-events/Build:33: pmu-events/pmu-events.o] Error 1
After the revert of 'perf-build-update-build-rule-for-generated-files.patch'
the build works again.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/10/05
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 0:17 ` Wang Yugui
@ 2023-10-06 10:12 ` Greg Kroah-Hartman
0 siblings, 0 replies; 25+ messages in thread
From: Greg Kroah-Hartman @ 2023-10-06 10:12 UTC (permalink / raw)
To: Wang Yugui
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor
On Thu, Oct 05, 2023 at 08:17:48AM +0800, Wang Yugui wrote:
> Hi,
>
> > This is the start of the stable review cycle for the 6.1.56 release.
> > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > and the diffstat can be found below.
>
> This 6.1.56-rc1 failed to build on rhel7 with dev-tool-set 8, but 6.1.55 works.
>
> Build error message:
> gcc: fatal error: no input files
> make[3]: *** [pmu-events/Build:33: pmu-events/pmu-events.o] Error 1
>
> After the revert of 'perf-build-update-build-rule-for-generated-files.patch'
> the build works again.
Offending patch dropped, thanks.
greg k-h
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
2023-10-04 19:33 ` Florian Fainelli
2023-10-05 0:17 ` Wang Yugui
@ 2023-10-05 0:59 ` Shuah Khan
2023-10-05 1:32 ` SeongJae Park
` (8 subsequent siblings)
11 siblings, 0 replies; 25+ messages in thread
From: Shuah Khan @ 2023-10-05 0:59 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor, Shuah Khan
On 10/4/23 11:52, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (2 preceding siblings ...)
2023-10-05 0:59 ` Shuah Khan
@ 2023-10-05 1:32 ` SeongJae Park
2023-10-05 3:41 ` Bagas Sanjaya
` (7 subsequent siblings)
11 siblings, 0 replies; 25+ messages in thread
From: SeongJae Park @ 2023-10-05 1:32 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, damon, SeongJae Park
Hello,
On Wed, 4 Oct 2023 19:52:53 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
This rc kernel passes DAMON functionality test[1] on my test machine.
Attaching the test results summary below. Please note that I retrieved the
kernel from linux-stable-rc tree[2].
Tested-by: SeongJae Park <sj@kernel.org>
[1] https://github.com/awslabs/damon-tests/tree/next/corr
[2] 0353a7bfd2b6 ("Linux 6.1.56-rc1")
Thanks,
SJ
[...]
---
# .config:1405:warning: override: reassigning to symbol DAMON
# .config:1415:warning: override: reassigning to symbol CGROUPS
ok 14 selftests: damon-tests: build_nomemcg.sh
# kselftest dir '/home/sjpark/damon-tests-cont/linux/tools/testing/selftests/damon-tests' is in dirty state.
# the log is at '/home/sjpark/log'.
[32m
ok 1 selftests: damon: debugfs_attrs.sh
ok 2 selftests: damon: debugfs_schemes.sh
ok 3 selftests: damon: debugfs_target_ids.sh
ok 4 selftests: damon: debugfs_empty_targets.sh
ok 5 selftests: damon: debugfs_huge_count_read_write.sh
ok 6 selftests: damon: debugfs_duplicate_context_creation.sh
ok 7 selftests: damon: sysfs.sh
ok 1 selftests: damon-tests: kunit.sh
ok 2 selftests: damon-tests: huge_count_read_write.sh
ok 3 selftests: damon-tests: buffer_overflow.sh
ok 4 selftests: damon-tests: rm_contexts.sh
ok 5 selftests: damon-tests: record_null_deref.sh
ok 6 selftests: damon-tests: dbgfs_target_ids_read_before_terminate_race.sh
ok 7 selftests: damon-tests: dbgfs_target_ids_pid_leak.sh
ok 8 selftests: damon-tests: damo_tests.sh
ok 9 selftests: damon-tests: masim-record.sh
ok 10 selftests: damon-tests: build_i386.sh
ok 11 selftests: damon-tests: build_arm64.sh
ok 12 selftests: damon-tests: build_i386_idle_flag.sh
ok 13 selftests: damon-tests: build_i386_highpte.sh
ok 14 selftests: damon-tests: build_nomemcg.sh
[33m
[92mPASS [39m
_remote_run_corr.sh SUCCESS
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (3 preceding siblings ...)
2023-10-05 1:32 ` SeongJae Park
@ 2023-10-05 3:41 ` Bagas Sanjaya
2023-10-05 12:27 ` Pavel Machek
` (6 subsequent siblings)
11 siblings, 0 replies; 25+ messages in thread
From: Bagas Sanjaya @ 2023-10-05 3:41 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
On Wed, Oct 04, 2023 at 07:52:53PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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.
>
Successfully compiled and installed bindeb-pkgs on my computer (Acer
Aspire E15, Intel Core i3 Haswell). No noticeable regressions.
Tested-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (4 preceding siblings ...)
2023-10-05 3:41 ` Bagas Sanjaya
@ 2023-10-05 12:27 ` Pavel Machek
2023-10-06 12:55 ` Greg Kroah-Hartman
2023-10-05 13:57 ` Takeshi Ogasawara
` (5 subsequent siblings)
11 siblings, 1 reply; 25+ messages in thread
From: Pavel Machek @ 2023-10-05 12:27 UTC (permalink / raw)
To: Greg Kroah-Hartman, sakari.ailus, davthompson
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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.
Here are some issues:
> Sakari Ailus <sakari.ailus@linux.intel.com>
> media: via: Use correct dependency for camera sensor drivers
> Sakari Ailus <sakari.ailus@linux.intel.com>
> media: v4l: Use correct dependency for camera sensor drivers
These are is unsuitable for 6.1 as the VIDEO_CAMERA_SENSOR symbol does
not exist in 6.1. Please drop.
> David Thompson <davthompson@nvidia.com>
> platform/mellanox: mlxbf-bootctl: add NET dependency into Kconfig
Unsuitable for stable, we don't have that problem in 5.10 or 6.1.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-6.1.y
Tested-by: Pavel Machek (CIP) <pavel@denx.de>
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 12:27 ` Pavel Machek
@ 2023-10-06 12:55 ` Greg Kroah-Hartman
0 siblings, 0 replies; 25+ messages in thread
From: Greg Kroah-Hartman @ 2023-10-06 12:55 UTC (permalink / raw)
To: Pavel Machek
Cc: sakari.ailus, davthompson, stable, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, jonathanh,
f.fainelli, sudipm.mukherjee, srw, rwarsow, conor
On Thu, Oct 05, 2023 at 02:27:40PM +0200, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 6.1.56 release.
> > There are 259 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.
>
> Here are some issues:
>
> > Sakari Ailus <sakari.ailus@linux.intel.com>
> > media: via: Use correct dependency for camera sensor drivers
> > Sakari Ailus <sakari.ailus@linux.intel.com>
> > media: v4l: Use correct dependency for camera sensor drivers
>
> These are is unsuitable for 6.1 as the VIDEO_CAMERA_SENSOR symbol does
> not exist in 6.1. Please drop.
It is in the 6.1.y tree, please look closer.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (5 preceding siblings ...)
2023-10-05 12:27 ` Pavel Machek
@ 2023-10-05 13:57 ` Takeshi Ogasawara
2023-10-05 16:39 ` Naresh Kamboju
` (4 subsequent siblings)
11 siblings, 0 replies; 25+ messages in thread
From: Takeshi Ogasawara @ 2023-10-05 13:57 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor
Hi Greg
On Thu, Oct 5, 2023 at 3:12 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
6.1.56-rc1 tested.
Build successfully completed.
Boot successfully completed.
No dmesg regressions.
Video output normal.
Sound output normal.
Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64) arch linux)
Thanks
Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com>
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (6 preceding siblings ...)
2023-10-05 13:57 ` Takeshi Ogasawara
@ 2023-10-05 16:39 ` Naresh Kamboju
2023-10-05 17:24 ` Petr Vorel
2023-10-06 18:42 ` Daniel Díaz
2023-10-05 18:40 ` Allen Pais
` (3 subsequent siblings)
11 siblings, 2 replies; 25+ messages in thread
From: Naresh Kamboju @ 2023-10-05 16:39 UTC (permalink / raw)
To: Greg Kroah-Hartman, linux-nfs
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, Olga Kornievskaia,
Benjamin Coddington, Anna Schumaker, Trond Myklebust, LTP List,
Petr Vorel, Richard Palethorpe, Eryu Guan, chrubis
On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Results from Linaro’s test farm.
Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
NFS mounted rootfs.
and LTP hugetlb hugemmap11 test case failed on x86 and arm64 bcm2711-rpi-4-b.
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
LTP hugetlb tests failed log
tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
LTP dio tests failed log
compare_file: char mismatch: infile offset 4096: 0x01 . outfile
offset 4096: 0x00 .
diotest01 1 TFAIL : diotest1.c:158: file compare failed for
infile and outfile
## Build
* kernel: 6.1.56-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-6.1.y
* git commit: 0353a7bfd2b60c5e42c8651eb3fa4cc48159db5f
* git describe: v6.1.55-260-g0353a7bfd2b6
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6
## Test Regressions (compared to v6.1.55)
* x86_64-clang, ltp-hugetlb
* bcm2711-rpi-4-b, ltp-hugetlb
* bcm2711-rpi-4-b-clang, ltp-hugetlb
* bcm2711-rpi-4-b-64k_page_size, ltp-hugetlb
- hugemmap11
Test log:
--------
tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
Links:
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6/testrun/20259639/suite/ltp-hugetlb/test/hugemmap11/log
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6/testrun/20260457/suite/ltp-hugetlb/test/hugemmap11/history/
* bcm2711-rpi-4-b, ltp-dio
* bcm2711-rpi-4-b-clang, ltp-dio
* bcm2711-rpi-4-b-64k_page_size, ltp-dio
- dio01
- dio02
- dio03
- dio05
- dio06
- dio07
- dio08
- dio09
- dio11
Test log:
--------
compare_file: char mismatch: infile offset 4096: 0x01 . outfile
offset 4096: 0x00 .
diotest01 1 TFAIL : diotest1.c:158: file compare failed for
infile and outfile
bufcmp: offset 0: Expected: 0x1, got 0x0
bufcmp: offset 0: Expected: 0x1, got 0x0
diotest02 1 TPASS : Read with Direct IO, Write without
diotest02 2 TFAIL : diotest2.c:119: read/write comparision failed
diotest02 3 TFAIL : diotest2.c:210: Write with Direct IO, Read without
diotest02 4 TFAIL : diotest2.c:119: read/write comparision failed
diotest02 5 TFAIL : diotest2.c:231: Read, Write with Direct IO
diotest02 0 TINFO : 2/3 testblocks failed
bufcmp: offset 0: Expected: 0x1, got 0x0
diotest03 1 TPASS : Read with Direct IO, Write without
diotest03 2 TFAIL : diotest3.c:136: comparsion failed; child=0 offset=0
diotest03 3 TFAIL : diotest3.c:189: Write Direct-child 0 failed
bufcmp: offset 0: Expected: 0x1, got 0x0
diotest03 1 TPASS : Read with Direct IO, Write without
diotest03 2 TFAIL : diotest3.c:306: Write with Direct IO, Read without
diotest03 3 TFAIL : diotest3.c:136: comparsion failed; child=0 offset=0
diotest03 4 TFAIL : diotest3.c:210: RDWR Direct-child 0 failed
diotest03 1 TPASS : Read with Direct IO, Write without
diotest03 2 TFAIL : diotest3.c:306: Write with Direct IO, Read without
diotest03 3 TFAIL : diotest3.c:323: Read, Write with Direct IO
...
diotest05 1 TPASS : Read with Direct IO, Write without
diotest05 2 TFAIL : diotest5.c:141: readv/writev comparision failed
diotest05 3 TFAIL : diotest5.c:250: Write with Direct IO, Read without
diotest05 4 TFAIL : diotest5.c:141: readv/writev comparision failed
diotest05 5 TFAIL : diotest5.c:271: Read, Write with Direct IO
diotest05 0 TINFO : 2/3 testblocks failed
Links:
- https://lkft.validation.linaro.org/scheduler/job/6842177#L1666
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6/testrun/20260389/suite/ltp-dio/test/dio01/history/
## Metric Regressions (compared to v6.1.55)
## Test Fixes (compared to v6.1.55)
## Metric Fixes (compared to v6.1.55)
## Test result summary
total: 121166, pass: 102582, fail: 2234, skip: 16177, xfail: 173
## Build Summary
* arc: 4 total, 4 passed, 0 failed
* arm: 140 total, 140 passed, 0 failed
* arm64: 49 total, 49 passed, 0 failed
* i386: 33 total, 33 passed, 0 failed
* mips: 24 total, 24 passed, 0 failed
* parisc: 3 total, 3 passed, 0 failed
* powerpc: 34 total, 34 passed, 0 failed
* riscv: 12 total, 12 passed, 0 failed
* s390: 12 total, 12 passed, 0 failed
* sh: 11 total, 11 passed, 0 failed
* sparc: 6 total, 6 passed, 0 failed
* x86_64: 40 total, 40 passed, 0 failed
## Test suites summary
* boot
* kselftest-android
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers-dma-buf
* kselftest-efivarfs
* kselftest-exec
* kselftest-filesystems
* kselftest-filesystems-binderfs
* kselftest-filesystems-epoll
* kselftest-firmware
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-net-forwarding
* kselftest-net-mptcp
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-user_events
* kselftest-vDSO
* kselftest-vm
* kselftest-watchdog
* kselftest-x86
* kselftest-zram
* kunit
* kvm-unit-tests
* libgpiod
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* perf
* rcutorture
* v4l2-compliance
--
Linaro LKFT
https://lkft.linaro.org
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 16:39 ` Naresh Kamboju
@ 2023-10-05 17:24 ` Petr Vorel
2023-10-05 19:20 ` Naresh Kamboju
2023-10-06 18:42 ` Daniel Díaz
1 sibling, 1 reply; 25+ messages in thread
From: Petr Vorel @ 2023-10-05 17:24 UTC (permalink / raw)
To: Naresh Kamboju
Cc: Greg Kroah-Hartman, linux-nfs, stable, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, conor,
Olga Kornievskaia, Benjamin Coddington, Anna Schumaker,
Trond Myklebust, LTP List, Richard Palethorpe, Eryu Guan, chrubis
Hi Naresh,
> On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > This is the start of the stable review cycle for the 6.1.56 release.
> > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > and the diffstat can be found below.
> > thanks,
> > greg k-h
> Results from Linaro’s test farm.
> Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
Could you please note in your reports also LTP version?
FYI the best LTP release is always the latest release or git master branch.
Kind regards,
Petr
> NFS mounted rootfs.
> and LTP hugetlb hugemmap11 test case failed on x86 and arm64 bcm2711-rpi-4-b.
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> LTP hugetlb tests failed log
> tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
> tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
> LTP dio tests failed log
> compare_file: char mismatch: infile offset 4096: 0x01 . outfile
> offset 4096: 0x00 .
> diotest01 1 TFAIL : diotest1.c:158: file compare failed for
> infile and outfile
> ## Build
> * kernel: 6.1.56-rc1
> * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
> * git branch: linux-6.1.y
> * git commit: 0353a7bfd2b60c5e42c8651eb3fa4cc48159db5f
> * git describe: v6.1.55-260-g0353a7bfd2b6
> * test details:
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6
> ## Test Regressions (compared to v6.1.55)
> * x86_64-clang, ltp-hugetlb
> * bcm2711-rpi-4-b, ltp-hugetlb
> * bcm2711-rpi-4-b-clang, ltp-hugetlb
> * bcm2711-rpi-4-b-64k_page_size, ltp-hugetlb
> - hugemmap11
> Test log:
> --------
> tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
> tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
> Links:
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6/testrun/20259639/suite/ltp-hugetlb/test/hugemmap11/log
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6/testrun/20260457/suite/ltp-hugetlb/test/hugemmap11/history/
> * bcm2711-rpi-4-b, ltp-dio
> * bcm2711-rpi-4-b-clang, ltp-dio
> * bcm2711-rpi-4-b-64k_page_size, ltp-dio
> - dio01
> - dio02
> - dio03
> - dio05
> - dio06
> - dio07
> - dio08
> - dio09
> - dio11
> Test log:
> --------
> compare_file: char mismatch: infile offset 4096: 0x01 . outfile
> offset 4096: 0x00 .
> diotest01 1 TFAIL : diotest1.c:158: file compare failed for
> infile and outfile
> bufcmp: offset 0: Expected: 0x1, got 0x0
> bufcmp: offset 0: Expected: 0x1, got 0x0
> diotest02 1 TPASS : Read with Direct IO, Write without
> diotest02 2 TFAIL : diotest2.c:119: read/write comparision failed
> diotest02 3 TFAIL : diotest2.c:210: Write with Direct IO, Read without
> diotest02 4 TFAIL : diotest2.c:119: read/write comparision failed
> diotest02 5 TFAIL : diotest2.c:231: Read, Write with Direct IO
> diotest02 0 TINFO : 2/3 testblocks failed
> bufcmp: offset 0: Expected: 0x1, got 0x0
> diotest03 1 TPASS : Read with Direct IO, Write without
> diotest03 2 TFAIL : diotest3.c:136: comparsion failed; child=0 offset=0
> diotest03 3 TFAIL : diotest3.c:189: Write Direct-child 0 failed
> bufcmp: offset 0: Expected: 0x1, got 0x0
> diotest03 1 TPASS : Read with Direct IO, Write without
> diotest03 2 TFAIL : diotest3.c:306: Write with Direct IO, Read without
> diotest03 3 TFAIL : diotest3.c:136: comparsion failed; child=0 offset=0
> diotest03 4 TFAIL : diotest3.c:210: RDWR Direct-child 0 failed
> diotest03 1 TPASS : Read with Direct IO, Write without
> diotest03 2 TFAIL : diotest3.c:306: Write with Direct IO, Read without
> diotest03 3 TFAIL : diotest3.c:323: Read, Write with Direct IO
> ...
> diotest05 1 TPASS : Read with Direct IO, Write without
> diotest05 2 TFAIL : diotest5.c:141: readv/writev comparision failed
> diotest05 3 TFAIL : diotest5.c:250: Write with Direct IO, Read without
> diotest05 4 TFAIL : diotest5.c:141: readv/writev comparision failed
> diotest05 5 TFAIL : diotest5.c:271: Read, Write with Direct IO
> diotest05 0 TINFO : 2/3 testblocks failed
> Links:
> - https://lkft.validation.linaro.org/scheduler/job/6842177#L1666
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.55-260-g0353a7bfd2b6/testrun/20260389/suite/ltp-dio/test/dio01/history/
> ## Metric Regressions (compared to v6.1.55)
> ## Test Fixes (compared to v6.1.55)
> ## Metric Fixes (compared to v6.1.55)
> ## Test result summary
> total: 121166, pass: 102582, fail: 2234, skip: 16177, xfail: 173
> ## Build Summary
> * arc: 4 total, 4 passed, 0 failed
> * arm: 140 total, 140 passed, 0 failed
> * arm64: 49 total, 49 passed, 0 failed
> * i386: 33 total, 33 passed, 0 failed
> * mips: 24 total, 24 passed, 0 failed
> * parisc: 3 total, 3 passed, 0 failed
> * powerpc: 34 total, 34 passed, 0 failed
> * riscv: 12 total, 12 passed, 0 failed
> * s390: 12 total, 12 passed, 0 failed
> * sh: 11 total, 11 passed, 0 failed
> * sparc: 6 total, 6 passed, 0 failed
> * x86_64: 40 total, 40 passed, 0 failed
> ## Test suites summary
> * boot
> * kselftest-android
> * kselftest-arm64
> * kselftest-breakpoints
> * kselftest-capabilities
> * kselftest-cgroup
> * kselftest-clone3
> * kselftest-core
> * kselftest-cpu-hotplug
> * kselftest-cpufreq
> * kselftest-drivers-dma-buf
> * kselftest-efivarfs
> * kselftest-exec
> * kselftest-filesystems
> * kselftest-filesystems-binderfs
> * kselftest-filesystems-epoll
> * kselftest-firmware
> * kselftest-fpu
> * kselftest-ftrace
> * kselftest-futex
> * kselftest-gpio
> * kselftest-intel_pstate
> * kselftest-ipc
> * kselftest-ir
> * kselftest-kcmp
> * kselftest-kexec
> * kselftest-kvm
> * kselftest-lib
> * kselftest-membarrier
> * kselftest-memfd
> * kselftest-memory-hotplug
> * kselftest-mincore
> * kselftest-mount
> * kselftest-mqueue
> * kselftest-net
> * kselftest-net-forwarding
> * kselftest-net-mptcp
> * kselftest-netfilter
> * kselftest-nsfs
> * kselftest-openat2
> * kselftest-pid_namespace
> * kselftest-pidfd
> * kselftest-proc
> * kselftest-pstore
> * kselftest-ptrace
> * kselftest-rseq
> * kselftest-rtc
> * kselftest-seccomp
> * kselftest-sigaltstack
> * kselftest-size
> * kselftest-splice
> * kselftest-static_keys
> * kselftest-sync
> * kselftest-sysctl
> * kselftest-tc-testing
> * kselftest-timens
> * kselftest-tmpfs
> * kselftest-tpm2
> * kselftest-user
> * kselftest-user_events
> * kselftest-vDSO
> * kselftest-vm
> * kselftest-watchdog
> * kselftest-x86
> * kselftest-zram
> * kunit
> * kvm-unit-tests
> * libgpiod
> * log-parser-boot
> * log-parser-test
> * ltp-cap_bounds
> * ltp-commands
> * ltp-containers
> * ltp-controllers
> * ltp-cpuhotplug
> * ltp-crypto
> * ltp-cve
> * ltp-dio
> * ltp-fcntl-locktests
> * ltp-filecaps
> * ltp-fs
> * ltp-fs_bind
> * ltp-fs_perms_simple
> * ltp-fsx
> * ltp-hugetlb
> * ltp-io
> * ltp-ipc
> * ltp-math
> * ltp-mm
> * ltp-nptl
> * ltp-pty
> * ltp-sched
> * ltp-securebits
> * ltp-smoke
> * ltp-syscalls
> * ltp-tracing
> * network-basic-tests
> * perf
> * rcutorture
> * v4l2-compliance
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 17:24 ` Petr Vorel
@ 2023-10-05 19:20 ` Naresh Kamboju
2023-10-06 6:41 ` Petr Vorel
0 siblings, 1 reply; 25+ messages in thread
From: Naresh Kamboju @ 2023-10-05 19:20 UTC (permalink / raw)
To: Petr Vorel
Cc: Greg Kroah-Hartman, linux-nfs, stable, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, conor,
Olga Kornievskaia, Benjamin Coddington, Anna Schumaker,
Trond Myklebust, LTP List, Richard Palethorpe, Eryu Guan, chrubis
On Thu, 5 Oct 2023 at 22:54, Petr Vorel <pvorel@suse.cz> wrote:
>
> Hi Naresh,
>
> > On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
>
> > > This is the start of the stable review cycle for the 6.1.56 release.
> > > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > > and the diffstat can be found below.
>
> > > thanks,
>
> > > greg k-h
>
> > Results from Linaro’s test farm.
> > Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
> Could you please note in your reports also LTP version?
Sure.
We are running LTP Version: 20230516 for our testing.
We will update the latest LTP release (20230929) next week.
> FYI the best LTP release is always the latest release or git master branch.
We have two threads here.
1) LTP release tag testing on all stable-rc branches
2) LTP master testing on a given specific kernel version [a]
[a] https://qa-reports.linaro.org/lkft/ltp-master/
- Naresh
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 19:20 ` Naresh Kamboju
@ 2023-10-06 6:41 ` Petr Vorel
0 siblings, 0 replies; 25+ messages in thread
From: Petr Vorel @ 2023-10-06 6:41 UTC (permalink / raw)
To: Naresh Kamboju
Cc: Greg Kroah-Hartman, linux-nfs, stable, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, conor,
Olga Kornievskaia, Benjamin Coddington, Anna Schumaker,
Trond Myklebust, LTP List, Richard Palethorpe, Eryu Guan, chrubis
> On Thu, 5 Oct 2023 at 22:54, Petr Vorel <pvorel@suse.cz> wrote:
> > Hi Naresh,
> > > On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > > This is the start of the stable review cycle for the 6.1.56 release.
> > > > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > > > and the diffstat can be found below.
> > > > thanks,
> > > > greg k-h
> > > Results from Linaro’s test farm.
> > > Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
> > Could you please note in your reports also LTP version?
> Sure.
> We are running LTP Version: 20230516 for our testing.
> We will update the latest LTP release (20230929) next week.
Great, thank you.
> > FYI the best LTP release is always the latest release or git master branch.
> We have two threads here.
> 1) LTP release tag testing on all stable-rc branches
> 2) LTP master testing on a given specific kernel version [a]
Great, this makes sense.
BTW from looking in the log [b] ("INFO: ltp-pan reported some tests FAIL")
I see you use runltp. We recommend to switch to kirk [c]. And we definitely
appreciate your feedback from it.
Kind regards,
Petr
> [a] https://qa-reports.linaro.org/lkft/ltp-master/
[b] https://qa-reports.linaro.org/lkft/ltp-master/build/v6.5.3_20230929-2-g48a150bfd/testrun/20223790/suite/ltp-cve/test/cve-2017-8890/log
[c] https://github.com/linux-test-project/kirk/#readme
> - Naresh
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-05 16:39 ` Naresh Kamboju
2023-10-05 17:24 ` Petr Vorel
@ 2023-10-06 18:42 ` Daniel Díaz
2023-10-07 8:58 ` Greg Kroah-Hartman
1 sibling, 1 reply; 25+ messages in thread
From: Daniel Díaz @ 2023-10-06 18:42 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Naresh Kamboju, linux-nfs, stable, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, conor,
Olga Kornievskaia, Benjamin Coddington, Anna Schumaker,
Trond Myklebust, LTP List, Petr Vorel, Richard Palethorpe,
Eryu Guan, chrubis
Hello!
On Thu, 5 Oct 2023 at 10:40, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.1.56 release.
> > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Results from Linaro’s test farm.
> Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
> NFS mounted rootfs.
> and LTP hugetlb hugemmap11 test case failed on x86 and arm64 bcm2711-rpi-4-b.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> LTP hugetlb tests failed log
> tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
> tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
>
> LTP dio tests failed log
> compare_file: char mismatch: infile offset 4096: 0x01 . outfile
> offset 4096: 0x00 .
> diotest01 1 TFAIL : diotest1.c:158: file compare failed for
> infile and outfile
Bisection led to "NFS: Fix O_DIRECT locking issues" (upstream commit
7c6339322ce0c6128acbe36aacc1eeb986dd7bf1). Reverting that patch and
"NFS: Fix error handling for O_DIRECT write scheduling" (upstream
commit 954998b60caa8f2a3bf3abe490de6f08d283687a) (not a clean revert
this one) made ltp-dio pass again.
Greetings!
Daniel Díaz
daniel.diaz@linaro.org
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-06 18:42 ` Daniel Díaz
@ 2023-10-07 8:58 ` Greg Kroah-Hartman
2023-10-09 16:43 ` Naresh Kamboju
0 siblings, 1 reply; 25+ messages in thread
From: Greg Kroah-Hartman @ 2023-10-07 8:58 UTC (permalink / raw)
To: Daniel Díaz
Cc: Naresh Kamboju, linux-nfs, stable, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, conor,
Olga Kornievskaia, Benjamin Coddington, Anna Schumaker,
Trond Myklebust, LTP List, Petr Vorel, Richard Palethorpe,
Eryu Guan, chrubis
On Fri, Oct 06, 2023 at 12:42:04PM -0600, Daniel Díaz wrote:
> Hello!
>
> On Thu, 5 Oct 2023 at 10:40, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 6.1.56 release.
> > > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > Results from Linaro’s test farm.
> > Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
> > NFS mounted rootfs.
> > and LTP hugetlb hugemmap11 test case failed on x86 and arm64 bcm2711-rpi-4-b.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > LTP hugetlb tests failed log
> > tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
> > tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> > hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
> >
> > LTP dio tests failed log
> > compare_file: char mismatch: infile offset 4096: 0x01 . outfile
> > offset 4096: 0x00 .
> > diotest01 1 TFAIL : diotest1.c:158: file compare failed for
> > infile and outfile
>
> Bisection led to "NFS: Fix O_DIRECT locking issues" (upstream commit
> 7c6339322ce0c6128acbe36aacc1eeb986dd7bf1). Reverting that patch and
> "NFS: Fix error handling for O_DIRECT write scheduling" (upstream
> commit 954998b60caa8f2a3bf3abe490de6f08d283687a) (not a clean revert
> this one) made ltp-dio pass again.
So this is also an issue in Linus's tree? Or is it only on the 6.1.y
tree.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-07 8:58 ` Greg Kroah-Hartman
@ 2023-10-09 16:43 ` Naresh Kamboju
0 siblings, 0 replies; 25+ messages in thread
From: Naresh Kamboju @ 2023-10-09 16:43 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Daniel Díaz, linux-nfs, stable, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, conor,
Olga Kornievskaia, Benjamin Coddington, Anna Schumaker,
Trond Myklebust, LTP List, Petr Vorel, Richard Palethorpe,
Eryu Guan, chrubis
On Sat, 7 Oct 2023 at 14:28, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Fri, Oct 06, 2023 at 12:42:04PM -0600, Daniel Díaz wrote:
> > Hello!
> >
> > On Thu, 5 Oct 2023 at 10:40, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > > On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > This is the start of the stable review cycle for the 6.1.56 release.
> > > > There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> > > > and the diffstat can be found below.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > >
> > > Results from Linaro’s test farm.
> > > Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
> > > NFS mounted rootfs.
> > > and LTP hugetlb hugemmap11 test case failed on x86 and arm64 bcm2711-rpi-4-b.
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >
> > > LTP hugetlb tests failed log
> > > tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
> > > tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> > > hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
> > >
> > > LTP dio tests failed log
> > > compare_file: char mismatch: infile offset 4096: 0x01 . outfile
> > > offset 4096: 0x00 .
> > > diotest01 1 TFAIL : diotest1.c:158: file compare failed for
> > > infile and outfile
> >
> > Bisection led to "NFS: Fix O_DIRECT locking issues" (upstream commit
> > 7c6339322ce0c6128acbe36aacc1eeb986dd7bf1). Reverting that patch and
> > "NFS: Fix error handling for O_DIRECT write scheduling" (upstream
> > commit 954998b60caa8f2a3bf3abe490de6f08d283687a) (not a clean revert
> > this one) made ltp-dio pass again.
>
> So this is also an issue in Linus's tree? Or is it only on the 6.1.y
It is only on the 6.1.y branch.
- Naresh
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (7 preceding siblings ...)
2023-10-05 16:39 ` Naresh Kamboju
@ 2023-10-05 18:40 ` Allen Pais
2023-10-05 22:17 ` Guenter Roeck
` (2 subsequent siblings)
11 siblings, 0 replies; 25+ messages in thread
From: Allen Pais @ 2023-10-05 18:40 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Compiled and booted on my x86_64 and ARM64 test systems. No errors or
regressions.
Tested-by: Allen Pais <apais@linux.microsoft.com>
Thanks.
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (8 preceding siblings ...)
2023-10-05 18:40 ` Allen Pais
@ 2023-10-05 22:17 ` Guenter Roeck
2023-10-06 7:30 ` Ron Economos
2023-10-06 9:32 ` Jon Hunter
11 siblings, 0 replies; 25+ messages in thread
From: Guenter Roeck @ 2023-10-05 22:17 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor
On Wed, Oct 04, 2023 at 07:52:53PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 157 pass: 155 fail: 2
Failed builds:
i386:tools/perf
x86_64:tools/perf
Qemu test results:
total: 529 pass: 529 fail: 0
Guenter
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (9 preceding siblings ...)
2023-10-05 22:17 ` Guenter Roeck
@ 2023-10-06 7:30 ` Ron Economos
2023-10-06 9:32 ` Jon Hunter
11 siblings, 0 replies; 25+ messages in thread
From: Ron Economos @ 2023-10-06 7:30 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, conor
On 10/4/23 10:52 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Tested-by: Ron Economos <re@w6rz.net>
^ permalink raw reply [flat|nested] 25+ messages in thread* Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
` (10 preceding siblings ...)
2023-10-06 7:30 ` Ron Economos
@ 2023-10-06 9:32 ` Jon Hunter
11 siblings, 0 replies; 25+ messages in thread
From: Jon Hunter @ 2023-10-06 9:32 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Greg Kroah-Hartman, patches, linux-kernel, torvalds, akpm, linux,
shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow, conor, linux-tegra, stable
On Wed, 04 Oct 2023 19:52:53 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.56 release.
> There are 259 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, 06 Oct 2023 17:51:12 +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.1.56-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v6.1:
10 builds: 10 pass, 0 fail
26 boots: 26 pass, 0 fail
116 tests: 116 pass, 0 fail
Linux version: 6.1.56-rc1-g0353a7bfd2b6
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra20-ventana, tegra210-p2371-2180,
tegra210-p3450-0000, tegra30-cardhu-a04
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Jon
^ permalink raw reply [flat|nested] 25+ messages in thread