From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.7 000/432] 6.7.12-rc1 review
Date: Wed, 3 Apr 2024 15:10:12 +0200 [thread overview]
Message-ID: <2024040349-labrador-corporate-cb6c@gregkh> (raw)
In-Reply-To: <CA+G9fYvc8axBi9Hm_WDac5v-4DiDmiFuKxk=Ghx80obEO9Uknw@mail.gmail.com>
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@linuxfoundation.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@linaro.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
next prev parent reply other threads:[~2024-04-03 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 15:39 [PATCH 6.7 000/432] 6.7.12-rc1 review Greg Kroah-Hartman
2024-04-01 15:43 ` [PATCH 6.7 225/432] drm/ttm: Make sure the mapped tt pages are decrypted when needed Greg Kroah-Hartman
2024-04-01 15:45 ` [PATCH 6.7 314/432] efi/libstub: fix efi_random_alloc() to allocate memory at alloc_min or higher address Greg Kroah-Hartman
2024-04-01 18:28 ` [PATCH 6.7 000/432] 6.7.12-rc1 review SeongJae Park
2024-04-01 19:04 ` Naresh Kamboju
2024-04-01 20:46 ` Florian Fainelli
2024-04-01 23:36 ` Shuah Khan
2024-04-02 5:05 ` Ron Economos
2024-04-02 8:06 ` Bagas Sanjaya
2024-04-02 9:12 ` Naresh Kamboju
2024-04-03 13:10 ` Greg Kroah-Hartman [this message]
2024-04-02 13:32 ` Justin Forbes
2024-04-02 14:40 ` Mark Brown
2024-04-02 19:14 ` Jon Hunter
2024-04-03 13:46 ` Conor Dooley
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=2024040349-labrador-corporate-cb6c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.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 \
/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;
as well as URLs for NNTP newsgroup(s).