From: Andrew Morton <akpm@osdl.org>
To: Christophe Saout <christophe@saout.de>
Cc: linux-kernel@vger.kernel.org, clemens@endorphin.org,
thornber@sistina.com
Subject: Re: loop driver, device-mapper and crypto
Date: Mon, 22 Dec 2003 14:03:05 -0800 [thread overview]
Message-ID: <20031222140305.61823850.akpm@osdl.org> (raw)
In-Reply-To: <1072129379.5570.73.camel@leto.cs.pocnet.net>
Christophe Saout <christophe@saout.de> wrote:
>
> In 2.6 we have a device-mapper which does such things in a much more
> generic way. I've already talked to a bunch of people working on loop
> and cryptoloop (also with Clemens Fruhwirth, the cryptoloop maintainer)
> and they all agreed that device-mapper is probably the most correct way
> to go, and would be happier if the loop driver was used for files only.
I'm not a crypto-loop user, so I am not in a position to judge whether
using dm for crypto-on-disk is feature-sufficient and adequate from an
operational point of view.
It is good that Joe-and-co are OK with it and are prepared to help support
it. If the people who _do_ use crypto-loop like the look of the feature
set and the user interface then fine. Certainly the loop driver has a long
history of not working very well.
So. If those-in-the-know like it then go wild. It would be useful to get
an opinion from the distro guys too.
However I suspect that there will be a migration issue, and that we should
continue to work to get crypto-loop functioning well, plan to remove it
from 2.8, yes?
next prev parent reply other threads:[~2003-12-22 22:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 21:42 loop driver, device-mapper and crypto Christophe Saout
2003-12-22 21:49 ` [PATCH 1/2] Add dm-daemon Christophe Saout
2003-12-23 12:27 ` Christoph Hellwig
2003-12-23 15:10 ` Joe Thornber
2003-12-22 21:52 ` [PATCH 2/2][RFC] Add dm-crypt target Christophe Saout
2003-12-22 23:07 ` Jeff Garzik
2003-12-22 23:24 ` Mike Fedyk
2003-12-22 23:29 ` Jeff Garzik
2003-12-22 23:50 ` Mike Fedyk
2003-12-23 0:10 ` Christophe Saout
2003-12-23 2:53 ` Rusty Russell
2003-12-23 13:13 ` Christoph Hellwig
2003-12-23 13:36 ` Christophe Saout
2003-12-23 15:15 ` Joe Thornber
2003-12-23 15:31 ` Jeff Garzik
2003-12-23 15:43 ` Joe Thornber
2003-12-23 17:01 ` Christophe Saout
2003-12-23 17:15 ` Joe Thornber
2003-12-23 17:14 ` Jeff Garzik
2003-12-22 22:03 ` Andrew Morton [this message]
2003-12-23 11:14 ` loop driver, device-mapper and crypto Fruhwirth Clemens
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=20031222140305.61823850.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=christophe@saout.de \
--cc=clemens@endorphin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thornber@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox