Re: Loop encryption module locking bug (linux-2.4.5).

2001-06-22 Thread Ingo Rohloff
> > Locking twice? But what happens if some program calls loop_set_status more > > than once? Losetup doesn't, but if such program exists, locking is still > > screwed. > > No, it calls loop_release_xfer always before init_xfer, which will release > the "permanent" use count. Calling lock twice

Re: Loop encryption module locking bug (linux-2.4.5).

2001-06-22 Thread Ingo Rohloff
Locking twice? But what happens if some program calls loop_set_status more than once? Losetup doesn't, but if such program exists, locking is still screwed. No, it calls loop_release_xfer always before init_xfer, which will release the permanent use count. Calling lock twice in

Re: Loop encryption module locking bug (linux-2.4.5).

2001-06-21 Thread Andreas Dilger
Ingo Rohloff writes: > PS: Because I try to understand the inner workings of the loop > device better, I have a question: > In lo_send is a loop: "while (len>0)". How can I configure > a loop device, so that this loop is executed more than once. > It seems this is only possible if

Re: Loop encryption module locking bug (linux-2.4.5).

2001-06-21 Thread Andi Kleen
I think your mail is offtopic for linux-kernel: it doesn't mention Microsoft or user space java programming or pointer to random unrelated web pages, but an actual kernel bug. Ingo Rohloff <[EMAIL PROTECTED]> writes: > > If lo_open doesn't call the cipher lock function and > lo_release

Loop encryption module locking bug (linux-2.4.5).

2001-06-21 Thread Ingo Rohloff
Hi, There is a bug in the locking scheme for the encryption functions, which can be hooked into the loop device. I have a patch which resolves the problem. First what happens: If you do (for example) a losetup -e twofish /dev/loop0 test.lop the following happens: The loop0 device gets opened

Loop encryption module locking bug (linux-2.4.5).

2001-06-21 Thread Ingo Rohloff
Hi, There is a bug in the locking scheme for the encryption functions, which can be hooked into the loop device. I have a patch which resolves the problem. First what happens: If you do (for example) a losetup -e twofish /dev/loop0 test.lop the following happens: The loop0 device gets opened

Re: Loop encryption module locking bug (linux-2.4.5).

2001-06-21 Thread Andi Kleen
sarcasm I think your mail is offtopic for linux-kernel: it doesn't mention Microsoft or user space java programming or pointer to random unrelated web pages, but an actual kernel bug. /sarcasm Ingo Rohloff [EMAIL PROTECTED] writes: If lo_open doesn't call the cipher lock function and

Re: Loop encryption module locking bug (linux-2.4.5).

2001-06-21 Thread Andreas Dilger
Ingo Rohloff writes: PS: Because I try to understand the inner workings of the loop device better, I have a question: In lo_send is a loop: while (len0). How can I configure a loop device, so that this loop is executed more than once. It seems this is only possible if