From: Jakub Kicinski <kuba@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
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, Netdev <netdev@vger.kernel.org>,
kunit-dev@googlegroups.com, Eric Dumazet <edumazet@google.com>,
chuck.lever@oracle.com
Subject: Re: [PATCH 6.5 000/321] 6.5.6-rc1 review
Date: Thu, 5 Oct 2023 07:34:08 -0700 [thread overview]
Message-ID: <20231005073408.6bb52351@kernel.org> (raw)
In-Reply-To: <CA+G9fYuH90g8jQ5SZHE98k16iQV5n+d2-G64xT9W9wrVmpt_Dg@mail.gmail.com>
It'd probably make sense to run the path to the test that's failing
thru get_maintainer and throw the right people on the CC. Adding Chuck.
On Thu, 5 Oct 2023 11:25:24 +0530 Naresh Kamboju wrote:
> On Wed, 4 Oct 2023 at 23:53, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.5.6 release.
> > There are 321 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.5.6-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.5.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> While running kunit testing on qemu-armv7 following test failures noticed
> on stable rc 6.5.6-rc1.
>
> # req_destroy works: EXPECTATION FAILED at net/handshake/handshake-test.c:477
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Test log:
> ----------
> <6>[ 1351.687335] KTAP version 1
> <6>[ 1351.688300] # Subtest: Handshake API tests
> <6>[ 1351.688760] 1..11
> <6>[ 1351.689362] KTAP version 1
> <6>[ 1351.689985] # Subtest: req_alloc API fuzzing
> <6>[ 1351.694360] ok 1 handshake_req_alloc NULL proto
> <6>[ 1351.705855] ok 2 handshake_req_alloc CLASS_NONE
> <6>[ 1351.710878] ok 3 handshake_req_alloc CLASS_MAX
> <6>[ 1351.715435] ok 4 handshake_req_alloc no callbacks
> <6>[ 1351.722026] ok 5 handshake_req_alloc no done callback
> <6>[ 1351.726579] ok 6 handshake_req_alloc excessive privsize
> <6>[ 1351.732397] ok 7 handshake_req_alloc all good
> <6>[ 1351.732934] # req_alloc API fuzzing: pass:7 fail:0 skip:0 total:7
> <6>[ 1351.733586] ok 1 req_alloc API fuzzing
> <6>[ 1351.741251] ok 2 req_submit NULL req arg
> <6>[ 1351.745979] ok 3 req_submit NULL sock arg
> <6>[ 1351.753307] ok 4 req_submit NULL sock->file
> <6>[ 1351.763090] ok 5 req_lookup works
> <6>[ 1351.770057] ok 6 req_submit max pending
> <6>[ 1351.774878] ok 7 req_submit multiple
> <6>[ 1351.782411] ok 8 req_cancel before accept
> <6>[ 1351.787423] ok 9 req_cancel after accept
> <6>[ 1351.795660] ok 10 req_cancel after done
> <3>[ 1351.799741] # req_destroy works: EXPECTATION FAILED at
> net/handshake/handshake-test.c:477
> <3>[ 1351.799741] Expected handshake_req_destroy_test == req, but
> <3>[ 1351.799741] handshake_req_destroy_test == 00000000
> <3>[ 1351.799741] req == cae22700
> <6>[ 1351.803368] not ok 11 req_destroy works
> <6>[ 1351.804539] # Handshake API tests: pass:10 fail:1 skip:0 total:11
> <6>[ 1351.805460] # Totals: pass:16 fail:1 skip:0 total:17
> <6>[ 1351.806276] not ok 95 Handshake API tests
>
> Links:
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.5.y/build/v6.5.5-322-g9327d0db36be/testrun/20257175/suite/kunit/test/req_alloc/log
> - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.5.y/build/v6.5.5-322-g9327d0db36be/testrun/20257175/suite/kunit/test/req_alloc/details/
> - https://storage.tuxsuite.com/public/linaro/lkft/builds/2WJGlCUgDzR8asQbd2BxMssFcEc/
> - https://storage.tuxsuite.com/public/linaro/lkft/builds/2WJGlCUgDzR8asQbd2BxMssFcEc/config
>
> Steps to reproduce:
> # To install tuxrun to your home directory at ~/.local/bin:
> # pip3 install -U --user tuxrun==0.49.2
> #
> # Or install a deb/rpm depending on the running distribution
> # See https://tuxmake.org/install-deb/ or
> # https://tuxmake.org/install-rpm/
> #
> # See https://tuxrun.org/ for complete documentation.
> Link to reproducer,
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2WJGlCUgDzR8asQbd2BxMssFcEc/tuxmake_reproducer.sh
>
> or
>
> tuxrun --runtime podman --device qemu-armv7 --boot-args rw --kernel
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2WJGlCUgDzR8asQbd2BxMssFcEc/zImage
> --modules https://storage.tuxsuite.com/public/linaro/lkft/builds/2WJGlCUgDzR8asQbd2BxMssFcEc/modules.tar.xz
> --rootfs https://storage.tuxboot.com/debian/bookworm/armhf/rootfs.ext4.xz
> --parameters SKIPFILE=skipfile-lkft.yaml --image
> docker.io/linaro/tuxrun-dispatcher:v0.49.2 --tests kunit --timeouts
> boot=30
>
>
> --
> Linaro LKFT
> https://lkft.linaro.org
>
prev parent reply other threads:[~2023-10-05 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231004175229.211487444@linuxfoundation.org>
2023-10-05 5:55 ` [PATCH 6.5 000/321] 6.5.6-rc1 review Naresh Kamboju
2023-10-05 14:34 ` Jakub Kicinski [this message]
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=20231005073408.6bb52351@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chuck.lever@oracle.com \
--cc=conor@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=ruanjinjie@huawei.com \
--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).