You mean how the bug was found? I originally reported this problem against
openSUSE 11.2 kernel, where when you have a dm-crypt loop filesystem the
container file modification time does not get updated with use. Consequence
of that is that backup runs would miss the fact container has changed.
Maybe one could argue it is a security feature in this scenario :), but as the
problem turns out to be unrelated to the crypto case, rather contained in the
loop driver itself, it looks like that would not hold.
Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
If we update mtime only during tear down, we might miss to backup after a
system crash or scenarios where the loop device is not deleted after use
during backup. Also when relatime is used, it is better to change mtime on
Thanks for taking the patch.