From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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,
Calum Mackay <calum.mackay@oracle.com>,
Chuck Lever III <chuck.lever@oracle.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
Darren Kenny <darren.kenny@oracle.com>,
Ramanan Govindarajan <ramanan.govindarajan@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 5.15 00/57] 5.15.155-rc1 review
Date: Fri, 12 Apr 2024 15:55:34 +0530 [thread overview]
Message-ID: <2c2362c7-ace7-4a79-861e-fa435e46ac85@oracle.com> (raw)
In-Reply-To: <20240411095407.982258070@linuxfoundation.org>
Hi Greg,
On 11/04/24 15:27, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.155 release.
> There are 57 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 Sat, 13 Apr 2024 09:53:55 +0000.
> Anything received after that time might be too late.
>
I have noticed a regression in lts test case with nfsv4 and this was
overlooked in the previous cycle(5.15.154). So the regression is from
153-->154 update. And I think that is due to nfs backports we had in
5.15.154.
# ./runltp -d /tmpdir -s fcntl17
<<<test_start>>>
tag=fcntl17 stime=1712915065
cmdline="fcntl17"
contacts=""
analysis=exit
<<<test_output>>>
fcntl17 0 TINFO : Enter preparation phase
fcntl17 0 TINFO : Exit preparation phase
fcntl17 0 TINFO : Enter block 1
fcntl17 0 TINFO : child 1 starting
fcntl17 0 TINFO : child 1 pid 22904 locked
fcntl17 0 TINFO : child 2 starting
fcntl17 0 TINFO : child 2 pid 22905 locked
fcntl17 0 TINFO : child 3 starting
fcntl17 0 TINFO : child 3 pid 22906 locked
fcntl17 0 TINFO : child 2 resuming
fcntl17 0 TINFO : child 3 resuming
fcntl17 0 TINFO : child 1 resuming
fcntl17 0 TINFO : child 3 lockw err 35
fcntl17 0 TINFO : child 3 exiting
fcntl17 0 TINFO : child 1 unlocked
fcntl17 0 TINFO : child 1 exiting
fcntl17 1 TFAIL : fcntl17.c:429: Alarm expired, deadlock not detected
fcntl17 0 TWARN : fcntl17.c:430: You may need to kill child
processes by hand
fcntl17 2 TPASS : Block 1 PASSED
fcntl17 0 TINFO : Exit block 1
fcntl17 0 TWARN : tst_tmpdir.c:342: tst_rmdir:
rmobj(/tmpdir/ltp-jRFBtBQhhx/LTP_fcnp7lqPn) failed:
unlink(/tmpdir/ltp-jRFBtBQhhx/LTP_fcnp7lqPn) failed; errno=2: ENOENT
<<<execution_status>>>
initiation_status="ok"
duration=10 termination_type=exited termination_id=5 corefile=no
cutime=0 cstime=0
<<<test_end>>>
<<<test_start>>>
tag=fcntl17_64 stime=1712915075
cmdline="fcntl17_64"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
fcntl17 0 TINFO : Enter preparation phase
fcntl17 0 TINFO : Exit preparation phase
fcntl17 0 TINFO : Enter block 1
fcntl17 0 TINFO : child 1 starting
fcntl17 0 TINFO : child 1 pid 22909 locked
fcntl17 0 TINFO : child 2 starting
fcntl17 0 TINFO : child 2 pid 22910 locked
fcntl17 0 TINFO : child 3 starting
fcntl17 0 TINFO : child 3 pid 22911 locked
fcntl17 0 TINFO : child 2 resuming
fcntl17 0 TINFO : child 3 resuming
fcntl17 0 TINFO : child 1 resuming
fcntl17 0 TINFO : child 3 lockw err 35
fcntl17 0 TINFO : child 3 exiting
fcntl17 0 TINFO : child 1 unlocked
fcntl17 0 TINFO : child 1 exiting
fcntl17 1 TFAIL : fcntl17.c:429: Alarm expired, deadlock not detected
fcntl17 0 TWARN : fcntl17.c:430: You may need to kill child
processes by hand
fcntl17 2 TPASS : Block 1 PASSED
fcntl17 0 TINFO : Exit block 1
fcntl17 0 TWARN : tst_tmpdir.c:342: tst_rmdir:
rmobj(/tmpdir/ltp-jRFBtBQhhx/LTP_fcn9Xy4hM) failed:
unlink(/tmpdir/ltp-jRFBtBQhhx/LTP_fcn9Xy4hM) failed; errno=2: ENOENT
<<<execution_status>>>
initiation_status="ok"
duration=10 termination_type=exited termination_id=5 corefile=no
cutime=0 cstime=0
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: 20240129-167-gb592cdd0d
Steps used after installing latest ltp:
$ mkdir /tmpdir
$ yum install nfs-utils -y
$ echo "/media *(rw,no_root_squash,sync)" >/etc/exports
$ systemctl start nfs-server.service
$ mount -o rw,nfsvers=3 127.0.0.1:/media /tmpdir
$ cd /opt/ltp
$ ./runltp -d /tmpdir -s fcntl17
This does not happen in 5.15.153 tag.
Adding nfs people to the CC list
Thanks,
Harshit
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.155-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-5.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
next parent reply other threads:[~2024-04-12 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240411095407.982258070@linuxfoundation.org>
2024-04-12 10:25 ` Harshit Mogalapalli [this message]
2024-04-12 10:50 ` [PATCH 5.15 00/57] 5.15.155-rc1 review Greg Kroah-Hartman
2024-04-12 15:57 ` Chuck Lever III
2024-04-12 20:06 ` Calum Mackay
2024-04-12 20:11 ` Harshit Mogalapalli
2024-04-12 20:23 ` Chuck Lever
2024-04-12 21:34 ` Harshit Mogalapalli
2024-04-13 15:56 ` Chuck Lever
2024-04-14 6:13 ` Greg Kroah-Hartman
2024-04-15 13:31 ` Chuck Lever
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=2c2362c7-ace7-4a79-861e-fa435e46ac85@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=calum.mackay@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=conor@kernel.org \
--cc=darren.kenny@oracle.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=ramanan.govindarajan@oracle.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 \
--cc=vegard.nossum@oracle.com \
/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).