pivot_root01 from ubuntu_ltp_syscalls failed on D-Oracle-5.0

Bug #1852966 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned
linux-aws (Ubuntu)
Invalid
Undecided
Unassigned
Disco
Invalid
Undecided
Unassigned
linux-signed-oracle (Ubuntu)
Invalid
Undecided
Unassigned
Disco
Invalid
Undecided
Unassigned

Bug Description

This issue can be reproduced with 5.0.0-1008.13-oracle, and the manually deployed 5.0.0-1005-oracle.

However, with the 5.0.0-1005.9-oracle regression testing report, this test was not failing by then, so it looks like a test case issue to me.

 tag=pivot_root01 stime=1573878599 dur=0 exit=exited stat=2 core=no cu=0 cs=0
 startup='Sat Nov 16 04:29:59 2019'
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 tst_test.c:345: BROK: Child (28591) killed by signal SIGSEGV

 Summary:
 passed 0
 failed 0
 skipped 0
 warnings 0

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
Uname: Linux 5.0.0-1005-oracle x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
Date: Mon Nov 18 06:24:57 2019
SourcePackage: linux-signed-oracle
UpgradeStatus: No upgrade log present (probably fresh install)

segfault could be found in dmesg:
[ 7120.889866] LTP: starting pivot_root01
[ 7120.891280] pivot_root01[8039]: segfault at 0 ip 0000561a27e9e5d0 sp 00007ffc196d79a0 error 4 in pivot_root01[561a27e97000+11000]
[ 7120.891285] Code: e7 53 4c 89 cb 48 89 de 48 81 ec 38 04 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 28 04 00 00 31 c0 4c 8b 8c 24 78 04 00 00 <f3> a6 0f 97 c0 1c 00 84 c0 0f 85 b1 00 00 00 b9 06 00 00 00 48 8d

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Po-Hsu Lin (cypressyew)
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Bisect shows this is ok until:
  ae52b6f4 (lib: Fix safe_mount() when mounting NTFS on kernels with NTFS support) [1]

But I can't tell why it has something to do this patch.

[1] https://github.com/linux-test-project/ltp/commit/ae52b6f41bf38da4a10e5fd7b036186d07cd17a1

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

More tests:
This test can pass on the same oracle instance by reverting commit ae52b6f4

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Spotted on T-AWS 4.4

 tag=pivot_root01 stime=1574067646 dur=0 exit=exited stat=2 core=no cu=0 cs=0
 startup='Mon Nov 18 09:00:46 2019'
 tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
 tst_test.c:345: BROK: Child (17480) killed by signal SIGSEGV

 Summary:
 passed 0
 failed 0
 skipped 0
 warnings 0

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Passed on B-AWS-5.0:
 startup='Sat Mar 7 01:19:10 2020'
 tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
 pivot_root01.c:158: PASS: pivot_root succeeded
 pivot_root01.c:173: PASS: pivot_root failed as expectedly: EBUSY (16)
 pivot_root01.c:173: PASS: pivot_root failed as expectedly: EINVAL (22)
 pivot_root01.c:173: PASS: pivot_root failed as expectedly: ENOTDIR (20)
 pivot_root01.c:173: PASS: pivot_root failed as expectedly: EPERM (1)

 Summary:
 passed 5
 failed 0
 skipped 0
 warnings 0
 tag=pivot_root01 stime=1583543950 dur=0 exit=exited stat=0 core=no cu=0 cs=0

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Passed with B-oracle-5.0 (5.0.0-1013.18)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Passed with T-aws-4.4 (4.4.0-1064.68-aws)

I think this can be safely closed.

Changed in linux-aws (Ubuntu):
status: New → Invalid
Changed in linux-aws (Ubuntu Disco):
status: New → Invalid
Changed in linux-signed-oracle (Ubuntu Disco):
status: New → Incomplete
status: Incomplete → Invalid
Changed in ubuntu-kernel-tests:
status: New → Fix Released
tags: added: ubuntu-ltp-syscalls
tags: added: aws oracle
Changed in linux-signed-oracle (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.