Skip to contentSkip to conversation

RFC(ry): breaking loop.c's IV calculation

DISCUSSION Jari Ruusu 2 participants 3 messages Dec 4, 2001 1 message not in the archive

lore
Share & tools
lore

Jari Ruusu

author
#1 lore raw
In reply to a message not in the archive
Quoted 2 lines · Herbert Valerio Riedel

well, I've put one patch together (it still needs (constructive) auditing though! jari?) here it is (it's against 2.4.16's loop.[ch])

I have attached my version of loop.c bug fixes. These are extracted from loop-AES and are well tested.

- IV computed in 512 byte units.
- Make device backed loop work with swap by pre-allocating pages.
- External encryption module locking bug fixed (from Ingo Rohloff).
- Get rid of the loop_get_bs() crap.
- grab_cache_page() return value handled properly, avoids Oops.
- No more illegal messing with BH_Dirty flag.
- No more illegal sleeping in generic_make_request().
- Loops can be set-up properly when root partition is still mounted ro.
- Default soft block size is set properly for file backed loops.
- kmalloc() error case handled properly.

Regards,
Jari Ruusu <[email protected]>

author
#3 lore raw
In reply to a message not in the archive
Quoted 2 lines · Herbert Valerio Riedel

well, I've put one patch together (it still needs (constructive) auditing though! jari?) here it is (it's against 2.4.16's loop.[ch])

1) For 2.4 kernels, IV type must remain int, not loop_iv_t, ok? Make the type loop_iv_t for 2.5 kernels but not for 2.4.

2) Get rid of the loop_get_bs() crap.

Regards,
Jari Ruusu <[email protected]>

#2 lore raw
In reply to Jari Ruusu

hello!

Quoted 6 lines · Jari Ruusu
Quoted 2 lines · Herbert Valerio Riedel

well, I've put one patch together (it still needs (constructive) auditing though! jari?) here it is (it's against 2.4.16's loop.[ch])

1) For 2.4 kernels, IV type must remain int, not loop_iv_t, ok? Make the type loop_iv_t for 2.5 kernels but not for 2.4.

no problem, the typedef can be changed to

typedef int loop_iv_t;

that way the API does not change; it just looks more consistent...

IMHO having a typedef in loop.h instead of hardcoding it to an 'int' is more flexible and less error-prone...

Quoted 1 line

2) Get rid of the loop_get_bs() crap.

btw, what's the motivation for it? I'd also like to know why it was used in the first place at all... :-)

Quoted 2 lines · Jari Ruusu

I have attached my version of loop.c bug fixes. These are extracted from loop-AES and are well tested.

although I'm quite confident you patch is well tested, it goes well beyond fixing only the IV calculation and as such represents a major change to the loop.c driver -- I'm curious whether it will be accepted for 2.4.x... :-) ; but don't get me wrong, I'll be quite happy if it goes in nevertheless!

just a minor note regarding source 'aesthetics';

it would be more self-explaining IMNSHO if you used some macro constant for the '9' shifting instead of hardcoding it...:

int IV = index * (PAGE_CACHE_SIZE >> 9) + (offset >> 9);

in your patch vs. in my patch:

/* loop.h */
#define LOOP_IV_SECTOR_BITS 9
#define LOOP_IV_SECTOR_SIZE (1 << LOOP_IV_SECTOR_BITS)

typedef int loop_iv_t;

/* loop.c */
const loop_iv_t IV =
(index << (PAGE_CACHE_SHIFT - LOOP_IV_SECTOR_BITS))
+ (offset >> LOOP_IV_SECTOR_BITS);

it makes also life easier for filters which include loop.h, cause you can check for the presence of the #defines above, whether a fixed loop.c is available or not; and we are also prepared for the (even if unlikely) event that those constants are changed some time...

Quoted 2 lines

- IV computed in 512 byte units.
- Make device backed loop work with swap by pre-allocating pages.

btw, just as a side note; IMHO this is a neat feature, but encrypted swap shouldn't be done on top of a loop device but more like the bsd people do it, as it allows for more interesting IV & key management schemes...

Quoted 8 lines

- External encryption module locking bug fixed (from Ingo Rohloff).
- Get rid of the loop_get_bs() crap.
- grab_cache_page() return value handled properly, avoids Oops.
- No more illegal messing with BH_Dirty flag.
- No more illegal sleeping in generic_make_request().
- Loops can be set-up properly when root partition is still mounted ro.
- Default soft block size is set properly for file backed loops.
- kmalloc() error case handled properly.

regards,

Signature · 4 lines
Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
Email: [email protected]       /    Finger [email protected] for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F
4142