From: "Jörn Engel" <joern@logfs.org>
To: Milan Broz <mbroz@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Prasad Joshi <prasadjoshi124@gmail.com>,
Witold Baryluk <baryluk@smp.if.uj.edu.pl>,
Aniket Sane <aniketsane@gmail.com>
Subject: Re: logfs: kernel NULL dereference
Date: Thu, 15 Sep 2011 16:52:04 +0200 [thread overview]
Message-ID: <20110915145204.GF24351@logfs.org> (raw)
In-Reply-To: <4E720B68.80809@redhat.com>
On Thu, 15 September 2011 16:27:52 +0200, Milan Broz wrote:
> On 09/14/2011 08:34 PM, Jörn Engel wrote:
> > Forwarded to dm-devel. Problem is a NULL pointer dereference in
> > kcryptd_io_read, which is triggered when mounting logfs. If someone
> > with device mapper knowledge could have a look, that would be useful.
> >
> > On Wed, 14 September 2011 20:24:25 +0200, Jörn Engel wrote:
> >>
> >> Ok, I can reliably reproduce the problem with the following, based on
> >> your description:
> >>
> >> truncate -s 0 foo
> >> truncate -s 1G foo
> >> losetup -v -f foo
> >> cryptsetup luksFormat /dev/loop0
> >> cryptsetup luksOpen /dev/loop0 foo
> >> pvcreate /dev/mapper/foo
> >> vgcreate our_volume /dev/mapper/foo
> >> lvcreate -L 128M -n logfstest our_volume
> >> yes yes | mklogfs /dev/mapper/our_volume-logfstest
> >> mount /dev/mapper/our_volume-logfstest /mnt/
>
> Which kernel version are you using?
Latest git - well, close to latest, given the current kernel.org trouble.
> >> It is a bit annoying that cryptsetup cannot easily be scripted.
>
> It can be easily scripted. (In quiet mode it will not ask for YES response, add -q,
> or just do "echo -n $PASSWORD | cryptsetup luksFormat ...")
Ok, I'll use that in the future. Thanks.
Jörn
--
More computing sins are committed in the name of efficiency (without
necessarily achieving it) than for any other single reason - including
blind stupidity.
-- W. A. Wulf
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2011-09-15 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110903125637.GG6092@smp.if.uj.edu.pl>
[not found] ` <20110907141527.GM32018@logfs.org>
[not found] ` <20110907210312.GA17634@smp.if.uj.edu.pl>
[not found] ` <20110907220856.GR32018@logfs.org>
[not found] ` <20110908161726.GA9104@smp.if.uj.edu.pl>
[not found] ` <20110914182425.GD24351@logfs.org>
2011-09-14 18:34 ` logfs: kernel NULL dereference Jörn Engel
2011-09-14 19:01 ` Witold Baryluk
2011-09-15 14:27 ` Milan Broz
2011-09-15 14:52 ` Jörn Engel [this message]
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=20110915145204.GF24351@logfs.org \
--to=joern@logfs.org \
--cc=aniketsane@gmail.com \
--cc=baryluk@smp.if.uj.edu.pl \
--cc=dm-devel@redhat.com \
--cc=mbroz@redhat.com \
--cc=prasadjoshi124@gmail.com \
/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.