1. Please describe the problem:

[   10.420422] BUG: sleeping function called from invalid context at include/crypto/algapi.h:426
[   10.420444] in_atomic(): 1, irqs_disabled(): 0, pid: 1224, name: cryptomgr_test
[   10.420451] 1 lock held by cryptomgr_test/1224:
[   10.420457]  #0: 00000000d138b6eb (ctrblk_lock){+.+.}, at: ctr_desall_crypt+0x42/0x230 [des_s390]
[   10.420470] CPU: 1 PID: 1224 Comm: cryptomgr_test Not tainted 5.2.0-0.rc2.git1.2.fc31.s390x #1
[   10.420476] Hardware name: IBM 2827 H43 400 (z/VM 6.4.0)
[   10.420483] Call Trace:
[   10.420493] ([<0000000023f4c4c6>] show_stack+0x8e/0xe8)
[   10.420503]  [<000000002483c528>] dump_stack+0x90/0xd0 
[   10.420512]  [<0000000023fba7d6>] ___might_sleep+0x24e/0x260 
[   10.420521]  [<00000000243d2c0c>] blkcipher_walk_done+0x2b4/0x2d0 
[   10.420530]  [<000003ff801012ca>] ctr_desall_crypt+0xf2/0x230 [des_s390] 
[   10.420541]  [<000003ff8010151a>] ctr_des_encrypt+0x3a/0x48 [des_s390] 
[   10.420546]  [<00000000243d3096>] skcipher_encrypt_blkcipher+0x6e/0x80 
[   10.420552]  [<00000000243dd55c>] test_skcipher_vec_cfg+0x244/0x8b0 
[   10.420557]  [<00000000243ddca0>] test_skcipher.isra.0+0xd8/0x110 
[   10.420561]  [<00000000243de920>] alg_test_skcipher+0xb8/0x188 
[   10.420566]  [<00000000243db55a>] alg_test+0x34a/0x4f8 
[   10.420571]  [<00000000243da3c0>] cryptomgr_test+0x68/0x70 
[   10.420577]  [<0000000023faffe0>] kthread+0x140/0x178 
[   10.420583]  [<00000000248628e4>] ret_from_fork+0x34/0x38 
[   10.420588] 1 lock held by cryptomgr_test/1224:
[   10.420592]  #0: 00000000d138b6eb (ctrblk_lock){+.+.}, at: ctr_desall_crypt+0x42/0x230 [des_s390]


2. What is the Version-Release number of the kernel:
kernel-5.2.0-0.rc2.git1.2.fc31.s390x


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

was also present in 5.1.0-0.rc3.git1.1.fc31.s390x


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

yes, just boot


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

yes

6. Are you running any modules that not shipped with directly Fedora's kernel?:

no


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.