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
>
On Fri, Apr 12, 2024 at 03:55:34PM +0530, Harshit Mogalapalli wrote:
> 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
Any way you can run 'git bisect' to find the offending change? There's
a lot to dig through :(
thanks,
greg k-h
> On Apr 12, 2024, at 6:25 AM, Harshit Mogalapalli <[email protected]> wrote:
>
> 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
The reproducer uses NFSv3, but the bug report says NFSv4
at the top.
I was able to reproduce this on my nfsd-5.15.y branch
with NFSv3.
A bisect would be most helpful.
> 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
--
Chuck Lever