** Description changed:
- This is a POTENTIAL REGRESSION.
+ This is a new test case added 4 days ago.
+ From the commit message it looks like this is a test case for a buggy commit
8db6c34f1dbc:
+ The regression is introduced from 8db6c34f1dbc ("Introduce v3 namespaced
+ file capabilities"). Overlayfs and possibly other networking filesystems
+ unhash the dentry on unlink, fail on this test with above change.
- PASSED with 4.4.0-1063-aws
- FAILED with 4.4.0-1064-aws in proposed
-
- This is a new test case added 4 days ago.
- From the commit message it looks like this is a test case for commit
8db6c34f1dbc:
- The regression is introduced from 8db6c34f1dbc ("Introduce v3 namespaced
- file capabilities"). Overlayfs and possibly other networking filesystems
- unhash the dentry on unlink, fail on this test with above change.
-
- However this commit has been applied in the Xenial AWS kernel
- (14985d791) with bug 1778286
+ This commit has been applied in the Xenial AWS kernel (14985d791) with
+ bug 1778286
This might have something to do with the way how we backport it (the
EINVAL return value is the clue)
-
<<<test_start>>>
tag=execveat03 stime=1534135632
cmdline="execveat03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL
Summary:
passed 0
failed 1
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
Uname: Linux 4.4.0-1064-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 13 04:51:09 2018
Ec2AMI: ami-529fb82a
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: x1e.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786729
Title:
execveat03 in ubuntu_ltp_syscalls failed on X/B
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
New
Status in linux-aws source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux-aws source package in Bionic:
New
Bug description:
This is a new test case added 4 days ago.
From the commit message it looks like this is a test case for a buggy commit
8db6c34f1dbc:
The regression is introduced from 8db6c34f1dbc ("Introduce v3 namespaced
file capabilities"). Overlayfs and possibly other networking filesystems
unhash the dentry on unlink, fail on this test with above change.
This commit has been applied in the Xenial AWS kernel (14985d791) with
bug 1778286
This might have something to do with the way how we backport it (the
EINVAL return value is the clue)
<<<test_start>>>
tag=execveat03 stime=1534135632
cmdline="execveat03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL
Summary:
passed 0
failed 1
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
Uname: Linux 4.4.0-1064-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 13 04:51:09 2018
Ec2AMI: ami-529fb82a
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: x1e.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786729/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
