msgrcv03 from ubuntu_ltp_syscalls failed on B-aws-4.15 ARM64

Bug #1904825 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned

Bug Description

Issue found on 4.15.0-1088.93-aws ARM64 instances (a1.2xlarge, a1.large, a1.medium)

 startup='Wed Nov 18 14:38:47 2020'
 CONFIG_CHECKPOINT_RESTORE
 ^
 Missing value

 tst_kconfig.c:475: TBROK: Invalid kconfig variables!
 tag=msgrcv03 stime=1605710327 dur=0 exit=exited stat=2 core=no cu=0 cs=0

Test failed because config requirement not met.

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

Here is the test log from 4.15.0-1087.92-aws with LTP Test suite HEAD SHA1: 62e322fad

 startup='Wed Oct 21 14:02:53 2020'
 tst_kconfig.c:62: TINFO: Parsing kernel config '/boot/config-4.15.0-1087-aws'
 tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
 msgrcv03.c:60: TINFO: EINVAL for MSG_COPY without IPC_NOWAIT
 msgrcv03.c:70: TPASS: msgrcv() failed as expected: EINVAL (22)
 msgrcv03.c:60: TINFO: EINVAL for MSG_COPY with MSG_EXCEPT
 msgrcv03.c:70: TPASS: msgrcv() failed as expected: EINVAL (22)
 msgrcv03.c:60: TINFO: ENOMSG with IPC_NOWAIT and MSG_COPY but with less than msgtyp messages
 msgrcv03.c:70: TPASS: msgrcv() failed as expected: ENOMSG (42)

 Summary:
 passed 3
 failed 0
 skipped 0
 warnings 0
 tag=msgrcv03 stime=1603288973 dur=0 exit=exited stat=0 core=no cu=0 cs=0

It looks like this commit upstream is the cause:
https://github.com/linux-test-project/ltp/commit/fdfa17f76b636b944ade511374ad1d282034f31c#diff-4c6ff7202c9730e476736ebe1e0475b19bbd777077f307f2b758328479ea56d6

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in ubuntu-kernel-tests:
status: New → In Progress
assignee: nobody → Po-Hsu Lin (cypressyew)
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in ubuntu-kernel-tests:
assignee: Po-Hsu Lin (cypressyew) → nobody
status: In Progress → Fix Released
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.