[Bug 1157339] New: modprobe loop.ko fails with key expired but secure boot is disabled
http://bugzilla.opensuse.org/show_bug.cgi?id=1157339 Bug ID: 1157339 Summary: modprobe loop.ko fails with key expired but secure boot is disabled Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: mail+novell@branleb.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I am trying to use the loop kernel module to mount a file/disk image. This failed always without a real error message, but took some time. $ sudo mount -t ext4 -o loop image.img /mnt mount: /mnt: mount failed: Operation not permitted. Some digging revealed that $ sudo modprobe loop would eventually fail everytime (but taking a lot of time, spawning a lot of child processes) whereas $ sudo insmod /lib/modules/$(uname -r)/kernel/drivers/block/loop.ko would succeed (and afterwards, This is a real problem because every other tool trying to load the module will use modprobe and fail (e.g. losetup). Additionally, the usual autoloading mechanisms for modules via /etc file will also use modprobe - and therefore not be successful. See these commands as an example: =============== florian-laptop:/home/florian # losetup -f losetup: cannot find an unused loop device: No such device florian-laptop:/home/florian # insmod /lib/modules/$(uname -r)/kernel/drivers/block/loop.ko ; echo $? 0 florian-laptop:/home/florian # lsmod | grep loop loop 32768 0 florian-laptop:/home/florian # losetup -f /dev/loop0 =============== modprobe apparently fails on calling insmod which is a bit confusing. Below is the complete output, but apparently the important line is "modprobe: ERROR: could not insert 'loop': Key has expired" which indicates that secure boot is the issue. But secure boot is disable in the BIOS and should not be the issue: ======= florian@florian-laptop:~> sudo dmesg | grep secure -i [ 0.000000] Secure boot could not be determined florian@florian-laptop:~> sudo mokutil --disable-validation This system does't support Secure Boot ======= ======================== florian-laptop:/home/florian # modprobe -v loop install /sbin/modprobe loop install /sbin/modprobe loop modprobe: INFO: custom logging function 0x55c9778e9540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x5621651ff540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x562c35061540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x55b446e72540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x55cf7aa4d540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x55b6183e9540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x5580aafc6540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x55aa7a337540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x55f03f9a5540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x563f1c3c2540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x564655fb2540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x5567fadcb540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x5620df145540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x56015bd7e540 registered install /sbin/modprobe loop modprobe: INFO: custom logging function 0x559cdfe9c540 registered install /sbin/modprobe loop modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Key has expired modprobe: INFO: context 0x559ce57ea630 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x56015c749760 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x5620e0614c10 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x5567fc332820 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x564657e39f20 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x563f1e0896c0 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x55f0416dd660 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x55aa7ad21a80 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x5580ac318440 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x55b619123e30 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x55cf7b0f85a0 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x55b4478c4050 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x562c355af790 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x5621658484e0 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: INFO: context 0x55c977e683f0 released modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted modprobe: ERROR: Error running install command for loop modprobe: ERROR: could not insert 'loop': Operation not permitted ======================== More System Information: ==================================== florian@florian-laptop:~> uname -a Linux florian-laptop.branleb 4.12.14-lp151.28.32-default #1 SMP Wed Nov 13 07:50:15 UTC 2019 (6e1aaad) x86_64 x86_64 x86_64 GNU/Linux florian@florian-laptop:~> zypper search --provides --match-exact /lib/modules/4.12.14-lp151.28.32-default/kernel/drivers/block/loop.ko Repository-Daten werden geladen... Installierte Pakete werden gelesen... S | Name | Zusammenfassung | Typ ---+----------------+---------------------+------ i+ | kernel-default | The Standard Kernel | Paket florian@florian-laptop:~> lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Leap 15.1 Release: 15.1 Codename: n/a florian-laptop:/home/florian # modinfo /lib/modules/4.12.14-lp151.28.32-default/kernel/drivers/block/loop.ko filename: /lib/modules/4.12.14-lp151.28.32-default/kernel/drivers/block/loop.ko alias: devname:loop-control alias: char-major-10-237 alias: block-major-7-* license: GPL suserelease: openSUSE Leap 15.1 srcversion: A2B95DC16A6A69C652EC6C9 depends: retpoline: Y intree: Y vermagic: 4.12.14-lp151.28.32-default SMP mod_unload modversions parm: max_loop:Maximum number of loop devices (int) parm: max_part:Maximum number of partitions per loop device (int) florian@florian-laptop:~> file /lib/modules/4.12.14-lp151.28.32-default/kernel/drivers/block/loop.ko /lib/modules/4.12.14-lp151.28.32-default/kernel/drivers/block/loop.ko: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), BuildID[sha1]=aff22c130b73c7f93113637d96ac2a76531acc6c, not stripped -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157339
http://bugzilla.opensuse.org/show_bug.cgi?id=1157339#c1
Takashi Iwai
$ sudo modprobe loop
would eventually fail everytime (but taking a lot of time, spawning a lot of child processes) whereas
$ sudo insmod /lib/modules/$(uname -r)/kernel/drivers/block/loop.ko
would succeed (and afterwards,
What does "modinfo loop | grep filename" show? Does it point to the very same module as you tried insmod? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com