[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
Ticket is already Fix Released - correcting the tags again ... ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Tags removed: architecture-s39031.64 ** Tags added: architecture-s39064 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
This bug was fixed in the package linux - 4.15.0-19.20 --- linux (4.15.0-19.20) bionic; urgency=medium * linux: 4.15.0-19.20 -proposed tracker (LP: #1766021) * Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers (LP: #1765232) - Revert "blk-mq: simplify queue mapping & schedule with each possisble CPU" - Revert "genirq/affinity: assign vectors to all possible CPUs" linux (4.15.0-18.19) bionic; urgency=medium * linux: 4.15.0-18.19 -proposed tracker (LP: #1765490) * [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm) (LP: #1765429) - powerpc/pseries: Fix clearing of security feature flags * signing: only install a signed kernel (LP: #1764794) - [Packaging] update to Debian like control scripts - [Packaging] switch to triggers for postinst.d postrm.d handling - [Packaging] signing -- switch to raw-signing tarballs - [Packaging] signing -- switch to linux-image as signed when available - [Config] signing -- enable Opal signing for ppc64el - [Packaging] printenv -- add signing options * [18.04 FEAT] Sign POWER host/NV kernels (LP: #1696154) - [Packaging] signing -- add support for signing Opal kernel binaries * Please cherrypick s390 unwind fix (LP: #1765083) - s390/compat: fix setup_frame32 * Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] (LP: #1751813) - d-i: move ipr to storage-core-modules on ppc64el * drivers/gpu/drm/bridge/adv7511/adv7511.ko missing (LP: #1764816) - SAUCE: (no-up) rename the adv7511 drm driver to adv7511_drm * Miscellaneous Ubuntu changes - [Packaging] Add linux-oem to rebuild test blacklist. linux (4.15.0-17.18) bionic; urgency=medium * linux: 4.15.0-17.18 -proposed tracker (LP: #1764498) * Eventual OOM with profile reloads (LP: #1750594) - SAUCE: apparmor: fix memory leak when duplicate profile load linux (4.15.0-16.17) bionic; urgency=medium * linux: 4.15.0-16.17 -proposed tracker (LP: #1763785) * [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed (LP: #1757346) - [Config]: Set CONFIG_PINCTRL_CANNONLAKE=y * [Ubuntu 18.04] USB Type-C test failed on GLK (LP: #1758797) - SAUCE: usb: typec: ucsi: Increase command completion timeout value * Fix trying to "push" an already active pool VP (LP: #1763386) - SAUCE: powerpc/xive: Fix trying to "push" an already active pool VP * hisi_sas: Revert and replace SAUCE patches w/ upstream (LP: #1762824) - Revert "UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to userspace" - Revert "UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES" - scsi: hisi_sas: modify some register config for hip08 - scsi: hisi_sas: add v3 hw MODULE_DEVICE_TABLE() * Realtek card reader - RTS5243 [VEN_10EC_5260] (LP: #1737673) - misc: rtsx: Move Realtek Card Reader Driver to misc - updateconfigs for Realtek Card Reader Driver - misc: rtsx: Add support for RTS5260 - misc: rtsx: Fix symbol clashes * Mellanox [mlx5] [bionic] UBSAN: Undefined behaviour in ./include/linux/net_dim.h (LP: #1763269) - net/mlx5e: Fix int overflow * apparmor bug fixes for bionic (LP: #1763427) - apparmor: fix logging of the existence test for signals - apparmor: make signal label match work when matching stacked labels - apparmor: audit unknown signal numbers - apparmor: fix memory leak on buffer on error exit path - apparmor: fix mediation of prlimit * dangling symlinks to loaded apparmor policy (LP: #1755563) // apparmor bug fixes for bionic (LP: #1763427) - apparmor: fix dangling symlinks to policy rawdata after replacement * [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock) (LP: #1762913) - powerpc/watchdog: remove arch_trigger_cpumask_backtrace * [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest (LP: #1762928) - powerpc/tm: Fix endianness flip on trap * Add support for RT5660 codec based sound cards on Baytrail (LP: #1657674) - SAUCE: (no-up) ASoC: Intel: Support machine driver for RT5660 on Baytrail - SAUCE: (no-up) ASoC: rt5660: Add ACPI support - SAUCE: (no-up): ASoC: Intel: bytcr-rt5660: Add MCLK, quirks - [Config] CONFIG_SND_SOC_INTEL_BYTCR_RT5660_MACH=m, CONFIG_SND_SOC_RT5660=m * /dev/ipmi enumeration flaky on Cavium Sabre nodes (LP: #1762812) - i2c: xlp9xx: return ENXIO on slave address NACK - i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly - i2c: xlp9xx: Check for Bus state before every transfer - i2c: xlp9xx: Handle NACK on DATA properly * [18.04 FEAT] Add kvm_stat from kernel tree (LP: #1734130) - tools/kvm_stat: simplify the sortkey function - tools/kvm_stat: use a namedtuple for storing the values - tools/kvm_stat: use a more pythonic way to iterate over dictionaries - tools/kvm_stat:
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
Bionic request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-April/091481.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Summary changed: - cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk + [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
