Skip to contentSkip to conversation

loop.c patches, take two

PATCH Andi Kleen 2 participants 2 messages Dec 22, 2003 10 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#10 lore raw
Quoted 10 lines · Christophe Saout

Am So, den 21.12.2003 schrieb Mika Penttilä um 21:49:

Quoted 5 lines

Yet another Big Loop Patch... :)

It's not obvious which parts are bug fixes, and which performance improvements. What exactly breaks loops on journalling filesystems, and how do you solve it?

What about dropping block device backed support for the loop driver altogether? We now have a nice device mapper in the 2.6 kernel. I don't

Device Mapper doesn't support cryptographic transformations.

-Andi

#11 lore raw

Am Mo, den 22.12.2003 schrieb Andi Kleen um 02:21:

Quoted 4 lines
Quoted 2 lines

What about dropping block device backed support for the loop driver altogether? We now have a nice device mapper in the 2.6 kernel. I don't

Device Mapper doesn't support cryptographic transformations.

I know. Not yet.

As I've written some lines below, there is a patch:
http://www.saout.de/misc/dm-crypt.diff that I've written some time ago.

I posted it some time ago but never got feedback from any "VIP" (except for Joe Thornber who helped developing the target and thinks it looks good). Some people tested it though and it worked for them (and better than cryptoloop around test4).

--
Christophe Saout <[email protected]>
Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html