kernel oops in LTP crypto test

[adamliyi]

For 4.14.49-8_nxgzip kernel:

reported in bug: 181254

[root@ltc-boston122 ~]# uname -a
Linux ltc-boston122.aus.stglabs.ibm.com 4.14.49-8_nxgzip.ppc64le #1 SMP Mon Sep 2 17:37:17 CST 2019 ppc64le ppc64le ppc64le GNU/Linux

Oct  2 00:44:36 ltc-boston122 LTP: starting crypto_user02
Oct  2 00:44:36 ltc-boston122 kernel: Unable to handle kernel paging request for data at address 0x00000000
Oct  2 00:44:36 ltc-boston122 kernel: Faulting instruction address: 0xc00000000051efd8
Oct  2 00:44:36 ltc-boston122 kernel: Oops: Kernel access of bad area, sig: 11 [#1]
Oct  2 00:44:36 ltc-boston122 kernel: LE SMP NR_CPUS=1024 NUMA PowerNV
Oct  2 00:44:36 ltc-boston122 kernel: Modules linked in: vmac snd_timer snd soundcore authenc pcrypt crypto_user salsa20_generic uinput msdos minix dummy veth nls_utf8 isofs binfmt_misc sctp brd fuse vfat fat btrfs xor zstd_decompress zstd_compress xxhash raid6_pq xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6_tables ib_isert iscsi_target_mod ib_srpt target_core_mod rpcrdma sunrpc ib_srp scsi_transport_srp ib_ucm rdma_ucm ib_uverbs ib_iser ib_umad rdma_cm iw_cm ib_ipoib libiscsi ib_cm scsi_transport_iscsi mlx5_ib ib_core ses enclosure at24 ofpart ipmi_powernv powernv_flash i2c_opal ipmi_devintf ipmi_msghandler mtd opal_prd xfs libcrc32c joydev ast i2c_algo_bit
Oct  2 00:44:36 ltc-boston122 kernel: drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm mlx5_core i2c_core mpt3sas i40e aacraid raid_class scsi_transport_sas
Oct  2 00:44:36 ltc-boston122 kernel: CPU: 112 PID: 38397 Comm: crypto_user02 Not tainted 4.14.49-8_nxgzip.ppc64le #1
Oct  2 00:44:36 ltc-boston122 kernel: task: c00020349020c180 task.stack: c000203972ce8000
Oct  2 00:44:36 ltc-boston122 kernel: NIP:  c00000000051efd8 LR: c00000000051fa8c CTR: c00000000051fa30
Oct  2 00:44:36 ltc-boston122 kernel: REGS: c000203972ceb580 TRAP: 0300   Not tainted  (4.14.49-8_nxgzip.ppc64le)
Oct  2 00:44:36 ltc-boston122 kernel: MSR:  9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE>  CR: 24002828  XER: 20040000
Oct  2 00:44:36 ltc-boston122 kernel: CFAR: c00000000051f318 DAR: 0000000000000000 DSISR: 40000000 SOFTE: 1 #012GPR00: c00000000051fa8c c000203972ceb800 c000000001426f00 c0002034e19fde00 #012GPR04: c000203972ceb8d0 0000000000000000 00000000fffeefff 0000000000000000 #012GPR08: 0000000000000000 c0002034e19fde00 ffffffff00000001 c008000027d413c8 #012GPR12: c00000000051fa30 c000000007d2d000 000000001001c330 00007fffdd1871c0 #012GPR16: 0000000010032de8 0000000010032df0 00007fffdd1870a8 00007fffdd1870b8 #012GPR20: 00007fffdd187088 0000000000000c1e c000203972ceb8d0 c000203972ceb820 #012GPR24: c000203972ceb840 c0002034e19fde10 0000000000000000 c0002034e19fde00 #012GPR28: c000203972ceb830 0000000000000000 0000000000000000 c000203972ceb8d0 
Oct  2 00:44:36 ltc-boston122 kernel: NIP [c00000000051efd8] crypto_remove_spawns+0x98/0x3e0
Oct  2 00:44:36 ltc-boston122 kernel: LR [c00000000051fa8c] crypto_unregister_instance+0x5c/0xa0
Oct  2 00:44:36 ltc-boston122 kernel: Call Trace:
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972ceb800] [c00000000171cf88] security_hook_heads+0x80/0xbd0 (unreliable)
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972ceb8b0] [c00000000051fa8c] crypto_unregister_instance+0x5c/0xa0
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972ceb900] [c008000027d40554] crypto_del_alg+0xd4/0x110 [crypto_user]
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972ceb930] [c008000027d40868] crypto_user_rcv_msg+0x128/0x260 [crypto_user]
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972ceb9e0] [c0000000009c087c] netlink_rcv_skb+0x15c/0x180
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972ceba50] [c008000027d4005c] crypto_netlink_rcv+0x4c/0x80 [crypto_user]
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972ceba80] [c0000000009bfbec] netlink_unicast+0x1fc/0x380
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972cebae0] [c0000000009c0230] netlink_sendmsg+0x350/0x480
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972cebb70] [c00000000093eea4] sock_sendmsg+0x64/0xa0
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972cebba0] [c00000000093fb1c] ___sys_sendmsg+0x30c/0x320
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972cebd30] [c00000000094114c] __sys_sendmsg+0x5c/0xc0
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972cebdd0] [c000000000941bac] SyS_socketcall+0x1cc/0x3d0
Oct  2 00:44:36 ltc-boston122 kernel: [c000203972cebe30] [c00000000000bfec] system_call+0x58/0x6c
Oct  2 00:44:36 ltc-boston122 kernel: Instruction dump:
Oct  2 00:44:36 ltc-boston122 kernel: 3b810030 82a90020 3ae10020 3b3b0010 fb010040 fb010048 fb810030 fb810038 
Oct  2 00:44:36 ltc-boston122 kernel: 7fbec840 7fddf378 fae10020 fae10028 <ebfe0000> 409e0028 480000b0 60000000 
Oct  2 00:44:36 ltc-boston122 kernel: ---[ end trace fb83a5498bc74611 ]---

[adamliyi]

As suggested by Haren, we need this upstream patch: torvalds@21d4120