New: cryptsetup luksOpen container_file container causes libdevmapper segfault

https://bugs.busybox.net/show_bug.cgi?id=10781

Bug ID: 10781
Summary: cryptsetup luksOpen container_file container causes
libdevmapper segfault
Product: buildroot
Version: 2018.02
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jsmr at gmx.de
CC: buildroot at uclibc.org
Target Milestone: ---

# creating container file works
dd if=/dev/urandom of=container_file bs=1M count=10
cryptsetup -y luksFormat container_file

cryptsetup --debug open container_file container

# cryptsetup 2.0.1 processing "cryptsetup --debug open container_file
container"
# Running command open.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device container_file.
# Trying to open and read device container_file with direct-io.
# Initialising device-mapper backend library.
# Trying to load any crypt type from device container_file.
# Crypto backend (OpenSSL 1.0.2n  7 Dec 2017) initialized in cryptsetup library
version 2.0.1.
# Detected kernel Linux 4.15.0 i686.
# PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0,
parallel_threads 0.
# Reading LUKS header of size 1024 from device container_file
# Key length 32, device size 20480 sectors, header size 2050 sectors.
# Activating volume container using token -1.
# Interactive passphrase entry requested.
Enter passphrase for container_file:
# Activating volume container [keyslot -1] using passphrase.
# dm version   [ opencount flush ]   [16384] (*1)
# dm versions   [ opencount flush ]   [16384] (*1)
# Detected dm-ioctl version 4.37.0.
# Device-mapper backend running with UDEV support disabled.
# dm status container  [ opencount flush ]   [16384] (*1)
Segmentation fault

dmesg
cryptsetup[150]: segfault at bf779fc4 ip b7eb6cf7 sp bf779fc8 error 6 in libdevmapper.so.1.02[b7e84000+44000]

I changed original supplied version 2.0.0 to 2.0.1 but it?s still not working.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10781

--- Comment #1 from Nobodyman <[email protected]> --- (In reply to Nobodyman from comment #0) Sorry, used command line was:
cryptsetup --debug luksOpen container_file container

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10781

--- Comment #2 from Nobodyman <[email protected]> --- Created attachment 7496
--> https://bugs.busybox.net/attachment.cgi?id=7496&action=edit
0001-libdm-iface.patch

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10781

--- Comment #3 from Nobodyman <[email protected]> --- This patch found on this site
https://gitlab.labs.nic.cz/turris/turris-os-packages/commit/8f08ed5f59b51b222aef72fb2902472b0fa068ad
was commited from Michal Hrusecky <[email protected]>. Original path: utils/lvm2/patches/004-dm_task_get_info.patch

lvm2: Fix crash and update to 2.02.145

Fixed really tricky issue with I suspect uClibc and devicemapper. For details see the patch. While at it updating it to the latest version as it didn't worked
anyway.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10781

--- Comment #4 from Thomas Petazzoni <[email protected]> --- This is in fact isn't really a Buildroot issue, more an upstream issue. I'm not a big fan of taking some random OpenWRT patch that isn't "obviously correct".

Has this issue been reported to the upstream lvm2 developers ? Or perhaps to the uClibc-ng maintainer ? I'm sure Waldemar will be interested about a case where a program against glibc works, but not with uClibc-ng.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10781

--- Comment #5 from wbx at openadk.org ---
I opened up an issue:
https://github.com/lvmteam/lvm2/issues/6

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10781

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #6 from Peter Korsgaard <[email protected]> --- This has now been fixed by:
https://git.buildroot.org/buildroot/commit/?id=5313c50aa3c1533c32ecf8d04c0628fbbb14f58d

You are receiving this mail because:
You are on the CC list for the bug.