Jens Axboe wrote:
>
<snip>
>
> The builtin transfer functions (none and xor) work with the changes,
> but external crypto additions may not. The reason is that the raw
> buf and loop buf passed to them can now be identical (the previous
> version always used getblk() to get a new buffer to work on).
>
<snip>
The crypto-api from the international kernel patch has recently defined
that the encryption functions contained in it must be able to encrypt
in-place. This maps directly to the loop-gen driver, so I don't see a
problem here. (Other than that there is no real patch-int-2.4.x out
there yet). However, the ciphers have not been checked to conform to
that definition.
Marc
--
Marc Mutz <[EMAIL PROTECTED]> http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics
PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
