Bug 1781863

Created attachment 1643705 [details]
dmesg for failing kernel 5.4.2

1. Please describe the problem:

With kernel-5.3.15, I can run singularity:
```
Linux localhost.localdomain 5.3.15-300.fc31.x86_64 #1 SMP Thu Dec 5 15:04:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[jeremiah@localhost ~]$ singularity run ./alpine_3.9.sif 
[jeremiah@localhost ~]$ echo $?
0
```

But with kernel-5.4.2, I get an error:
```
[jeremiah@localhost ~]$ uname -a
Linux localhost.localdomain 5.4.2-300.fc31.x86_64 #1 SMP Fri Dec 6 13:07:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[jeremiah@localhost ~]$ singularity run ./alpine_3.9.sif 
FATAL:   container creation failed: mount /proc/self/fd/3->/var/singularity/mnt/session/rootfs error: can't mount image /proc/self/fd/3: kernel reported a bad superblock for squashfs image partition, possible causes are that your kernel doesn't support the compression algorithm or the image is corrupted
```

2. What is the Version-Release number of the kernel:

5.4.2-300


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 :

5.4.2-300


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

$ singularity pull --arch amd64 library://library/default/alpine:3.9
$ singularity run ./alpine_3.9.sif



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.