All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10781] New: cryptsetup luksOpen container_file container causes libdevmapper segfault
Date: Mon, 19 Feb 2018 22:41:29 +0000	[thread overview]
Message-ID: <bug-10781-163@https.bugs.busybox.net/> (raw)

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.

             reply	other threads:[~2018-02-19 22:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 22:41 bugzilla at busybox.net [this message]
2018-02-19 22:50 ` [Buildroot] [Bug 10781] cryptsetup luksOpen container_file container causes libdevmapper segfault bugzilla at busybox.net
2018-03-01 20:16 ` bugzilla at busybox.net
2018-03-02 22:31 ` bugzilla at busybox.net
2018-06-06 13:41 ` bugzilla at busybox.net
2018-06-10  4:33 ` bugzilla at busybox.net
2018-08-20  8:48 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-10781-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.