add_key01 from ubuntu_ltp_syscalls failed on Bionic s390x

Bug #1862878 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 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Issue found on s2lp3 s390x Ubuntu LPAR
Test failed with:
  add_key01.c:77: FAIL: add_key call failed unexpectedly: ENOMEM (12)

<<<test_start>>>
tag=add_key01 stime=1581482840
cmdline="add_key01"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_buffers.c:55: INFO: Test is using guarded buffers
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
add_key01.c:63: INFO: The key type is keyrings and plen is 0
add_key01.c:79: PASS: add_key call succeeded as expected
add_key01.c:63: INFO: the key type is keyrings and plen is 1
add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)
add_key01.c:63: INFO: The key type is user and plen is 32767
add_key01.c:79: PASS: add_key call succeeded as expected
add_key01.c:63: INFO: The key type is user and plen is 32768
add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)
add_key01.c:63: INFO: The key type is logon and plen is 32767
add_key01.c:79: PASS: add_key call succeeded as expected
add_key01.c:63: INFO: The key type is logon and plen is 32768
add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)
add_key01.c:63: INFO: The key type is big_key and plen is 1048575
add_key01.c:77: FAIL: add_key call failed unexpectedly: ENOMEM (12)
add_key01.c:63: INFO: The key type is big_key and plen is 1048576
add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)

Summary:
passed 7
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>>>

dmesg output:
[ 847.773454] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 847.773603] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 848.733118] LTP: starting add_key01
[ 848.736003] WARNING: CPU: 2 PID: 4833 at /build/linux-Vp68rX/linux-4.15.0/mm/page_alloc.c:4230 __alloc_pages_nodemask+0x28e/0xfe8
[ 848.736004] Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge iptable_filter overlay openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack 8021q garp stp mrp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) dm_service_time zcommon(PO) znvpair(PO) spl(O) dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua qeth_l2 genwqe_card crc_itu_t chsc_sch eadm_sch qeth ctcm ccwgroup fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm nfsd iw_cm ib_cm auth_rpcgss iscsi_tcp libiscsi_tcp libiscsi nfs_acl lockd scsi_transport_iscsi grace sunrpc ip_tables x_tables
[ 848.736051] btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx4_en mlx4_ib ib_core ptp pps_core crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core devlink zfcp qdio scsi_transport_fc dasd_eckd_mod dasd_mod
[ 848.736077] CPU: 2 PID: 4833 Comm: add_key01 Tainted: P O 4.15.0-87-generic #87-Ubuntu
[ 848.736077] Hardware name: IBM 2964 N63 400 (LPAR)
[ 848.736079] Krnl PSW : 000000004532b723 000000000968d01f (__alloc_pages_nodemask+0x28e/0xfe8)
[ 848.736082] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
[ 848.736083] Krnl GPRS: 0000000000000000 0000000000000001 00000000014040c0 0000000000000009
[ 848.736084] 0000000000000000 0000000000000000 00000000000fffff 0000000000000009
[ 848.736085] 000000000050663c 000000000010000f 00000000014000c0 00000000000fffff
[ 848.736086] 0000000000000000 0000000000943a68 00000003b436fc90 00000003b436fb00
[ 848.736094] Krnl Code: 00000000002e16b2: a7210200 tmll %r2,512
                          00000000002e16b6: a774ff4a brc 7,00000000002e154a
                         #00000000002e16ba: a7f40001 brc 15,00000000002e16bc
                         >00000000002e16be: a7f4ff46 brc 15,00000000002e154a
                          00000000002e16c2: a7080000 lhi %r0,0
                          00000000002e16c6: a7f4ff08 brc 15,00000000002e14d6
                          00000000002e16ca: e31003380004 lg %r1,824
                          00000000002e16d0: 5810101c l %r1,28(%r1)
[ 848.736106] Call Trace:
[ 848.736108] ([<00000003b436faf8>] 0x3b436faf8)
[ 848.736112] [<000000000030e328>] kmalloc_order_trace+0x48/0x120
[ 848.736116] [<000000000050663c>] big_key_preparse+0x7c/0x210
[ 848.736117] [<00000000004fdf20>] key_create_or_update+0x120/0x470
[ 848.736119] [<00000000005002dc>] SyS_add_key+0xf4/0x220
[ 848.736122] [<00000000008fa788>] system_call+0xdc/0x2c8
[ 848.736123] Last Breaking-Event-Address:
[ 848.736124] [<00000000002e16ba>] __alloc_pages_nodemask+0x28a/0xfe8
[ 848.736125] ---[ end trace 15ff0cd6918f24ba ]---

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-87-generic 4.15.0-87.87
ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
Uname: Linux 4.15.0-87-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Wed Feb 12 04:10:36 2020
HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 crashkernel=196M audit=0 BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-87-generic N/A
 linux-backports-modules-4.15.0-87-generic N/A
 linux-firmware 1.173.15
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
tags: added: 4.15 sru-20200127 ubuntu-ltp-syscalls
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue seems to related to the latest change in LTP for this test case
https://github.com/linux-test-project/ltp/commit/c50f05195ac1c6c62749fee360f1cfbba2606407

With this test reverted, the test result will be:
<<<test_start>>>
tag=add_key01 stime=1581483125
cmdline="add_key01"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
add_key01.c:21: PASS: add_key call succeeded

Summary:
passed 1
failed 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=0 corefile=no
cutime=0 cstime=0
<<<test_end>>>

dmesg output:

[ 1132.663932] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 1132.664848] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 1133.521332] LTP: starting add_key01

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Didn't see this in this cycle 4.15.0-114.115 on s2lp3.

Let's keep an eye on this for another cycle.

Changed in ubuntu-kernel-tests:
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Passed with 4.15.0-126.129-generic on B s390x LPAR / zVM
Closing this bug

Changed in ubuntu-kernel-tests:
status: Incomplete → Fix Released
Changed in linux (Ubuntu):
status: Confirmed → 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.