a43e2a0d8e
For certain combinations of sectorsize, mediasize and random numbers (used to define the mapping), a multisector read or write would ignore some subset of the sectors past the first sector in the request because those sectors would be mapped past the end of the parent device, and normal "end of media" truncation would zap that part of the request. Rev 1.19+1.20 of g_bde_work.c added the check which should have alerted me to this happening. This commit maps the request correctly and adds KASSERTS to make sure things stay inside the parent device. This does not change the on-disk layout of GBDE, there is no need to backup/restore. |
||
---|---|---|
.. | ||
g_bde_crypt.c | ||
g_bde_lock.c | ||
g_bde_work.c | ||
g_bde.c | ||
g_bde.h |