[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024040349-labrador-corporate-cb6c@gregkh>
Date: Wed, 3 Apr 2024 15:10:12 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
jonathanh@...dia.com, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
conor@...nel.org, allen.lkml@...il.com, broonie@...nel.org
Subject: Re: [PATCH 6.7 000/432] 6.7.12-rc1 review
On Tue, Apr 02, 2024 at 02:42:29PM +0530, Naresh Kamboju wrote:
> On Mon, 1 Apr 2024 at 21:41, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > Note, this will be the LAST 6.7.y kernel release. After this one it
> > will be end-of-life. Please move to 6.8.y now.
> >
> > ------------------------------------------
> >
> > This is the start of the stable review cycle for the 6.7.12 release.
> > There are 432 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 Wed, 03 Apr 2024 15:24:46 +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.7.12-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.7.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Results from Linaro’s test farm.
> Regressions on arm64, arm, x86_64, and i386 with libgpiod tests.
>
> libgpiod test regressions noticed on Linux stable-rc 6.8, 6.7 and 6.6
> and Linux next and mainline master.
>
> Anders bisected and found this first bad commit,
> gpio: cdev: sanitize the label before requesting the interrupt
> commit b34490879baa847d16fc529c8ea6e6d34f004b38 upstream.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> LKFT is running libgpiod test suite version
> v2.0.1-0-gae275c3 (and also tested v2.1)
>
> libgpiod
> - _gpiod_edge-event_edge_event_wait_timeout
> - _gpiod_edge-event_event_copy
> - _gpiod_edge-event_null_buffer
> - _gpiod_edge-event_read_both_events
> - _gpiod_edge-event_read_both_events_blocking
> - _gpiod_edge-event_read_falling_edge_event
> - _gpiod_edge-event_read_rising_edge_event
> - _gpiod_edge-event_read_rising_edge_event_polled
> - _gpiod_edge-event_reading_more_events_than_the_queue_contains_doesnt_block
> - _gpiod_edge-event_seqno
> - _gpiod_line-info_edge_detection_settings
>
> Test log:
> -------
> ok 16 /gpiod/edge-event/edge_event_buffer_max_capacity
> **
> gpiod-test:ERROR:tests-edge-event.c:52:_gpiod_test_func_edge_event_wait_timeout:
> '_request' should not be NULL
> # gpiod-test:ERROR:tests-edge-event.c:52:_gpiod_test_func_edge_event_wait_timeout:
> '_request' should not be NULL
> not ok 17 /gpiod/edge-event/edge_event_wait_timeout
> ok 18 /gpiod/edge-event/cannot_request_lines_in_output_mode_with_edge_detection
> **
> gpiod-test:ERROR:tests-edge-event.c:125:_gpiod_test_func_read_both_events:
> '_request' should not be NULL
> # gpiod-test:ERROR:tests-edge-event.c:125:_gpiod_test_func_read_both_events:
> '_request' should not be NULL
> not ok 19 /gpiod/edge-event/read_both_events
>
> Links:
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.7.y/build/v6.7.11-433-gb15156435f06/testrun/23252698/suite/libgpiod/tests/
I'm going to drop the gpio change and make it for the next round of
stable kernels, so we don't get this regression.
thanks,
greg k-h
Powered by blists - more mailing lists