From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10781] cryptsetup luksOpen container_file container causes libdevmapper segfault
Date: Wed, 06 Jun 2018 13:41:10 +0000 [thread overview]
Message-ID: <bug-10781-163-x8ZV7UtTzT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10781-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10781
--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
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.
next prev parent reply other threads:[~2018-06-06 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 22:41 [Buildroot] [Bug 10781] New: cryptsetup luksOpen container_file container causes libdevmapper segfault bugzilla at busybox.net
2018-02-19 22:50 ` [Buildroot] [Bug 10781] " 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 [this message]
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-x8ZV7UtTzT@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.