On Sun, 13 Feb 2000, Andi Kleen wrote:
> Nothing.
>
> The additional information is whether the disk image uses the absolute
> or the relative IVs.
>
> The bad part of the change is to make the relative IV the default, it needs
> to be an optional feature for new filter modules that know what they are
> doing (or that they don't need to worry about backwards compatibility)
It does not, if your module for 2.4 will care to call ->bmap(). It should
know that it gets relative IV. And that's known from the kernel version.
It can trivially convert them to absolute ones, if that's what you want.
_If_ you want the same encryption + relative ones used in format - yes, you
got a new format and need a new module.
> The way to do that is to add new function vectors to loop_func_table.
What for? How will this new function differ from the old one? Let's just
_always_ pass the relative block number and if your module wants absolute
it can trivially get them. See the code I've sent to you.
Yes, it's an incompatibility between the 2.2 and 2.3/2.4. Trivially solvable
one. IMO it's not worth adding a new method - _that_ will give you binary
incompatibility anyway.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:23 EST