From: jassi brar <jassi_singh_brar@yahoo.com>
To: Kasper Sandberg <lkml@metanurb.dk>, Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: An idea .... with code
Date: Wed, 27 Aug 2008 18:24:02 -0700 (PDT) [thread overview]
Message-ID: <200298.8282.qm@web33207.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080827150221.GV26610@one.firstfloor.org>
--- On Wed, 8/27/08, Andi Kleen <andi@firstfloor.org> wrote:
> On Wed, Aug 27, 2008 at 04:49:35PM +0200, Kasper Sandberg
> wrote:
> > As far as cryptoloop goes, isnt that obsoleted anyway?
>
> It's like saying: FAT -- isn't that obsolete by
> now?
> As long as there are crypto loop files around it's not
> obsolete.
Cryptoloop? No, my code isn't the 'same' as loop.c and hence can't provide for cryptoloop. I lose, you win :)
Cryptoloop was designed so b'coz 'loop' feature was available, not the other way round. Had we not had '-o loop', developers would have devised mechanism for encrypting block devices rather than exploiting the -o loop hack. In retrospect, it seems Cryptoloop was a bad design based upon a hack.
Encryption? Yes, my code does provide a way for it. It supports better dm-crypt/LUKS off the shelf.
Loop.c sure provides more 'features' but the point is that we can make do without them, which only adds to the complexity. A simpler and more generic driver could do us equal good.
> > is there anyone
> > that doesent use dm-crypt by now?
> Wrong question. You lose.
I see one mail from Andrew Morton suggesting removal of cryptoloop altogether in order to ramp up its obsoletion! I am only providing a more-transparent-way of using dm-crypt.
I assume the concede Kasper's point on 'offset' feature of loop.c.
Anyways, seems we are moving from discussion to debate. You've got the whole picture and now its purely your call to approve of it or not.
Better still, you could suggest how to make it better: we are for sure gonna drop cryptoloop for dm-crypt. What wud we do with the then-unnecessary crypt support of loop.c?
Or maybe, for the time being, it would be better to modify Loop.c to allow for runtime alloc/free of as many resources as needed and provide for sysfs interface to add/remove 'loop' rather than ioctls?
I had an idea and i cooked up a code. I wanted to put it somewhere for someone to stumble upon the idea sometime. I am done.
Best Regards,
-Jassi
next prev parent reply other threads:[~2008-08-28 1:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 8:53 An idea .... with code jassi brar
2008-08-25 12:22 ` Jochen Voß
2008-08-25 20:53 ` Marcin Slusarz
2008-08-26 2:47 ` Bill Davidsen
2008-08-26 8:24 ` Andi Kleen
2008-08-26 10:44 ` Alexey Dobriyan
2008-08-26 11:08 ` Andi Kleen
2008-08-27 7:24 ` jassi brar
2008-08-27 7:47 ` Andi Kleen
2008-08-27 9:57 ` David Newall
2008-08-27 10:01 ` Andi Kleen
2008-08-27 12:38 ` jassi brar
2008-08-27 12:47 ` Andi Kleen
2008-08-27 14:49 ` Kasper Sandberg
2008-08-27 15:02 ` Andi Kleen
2008-08-28 1:24 ` jassi brar [this message]
2008-08-28 9:41 ` Kasper Sandberg
2008-08-30 2:57 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2008-08-27 0:44 jassi brar
2008-08-27 2:27 jassi brar
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=200298.8282.qm@web33207.mail.mud.yahoo.com \
--to=jassi_singh_brar@yahoo.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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