[Bug 242448] Re: Hardy ecryptfs can cause data loss

[Serge Hallyn]

Well uname says I'm running 2.6.24-22-generic, but the ecryptfs bug
isn't showing up right now.

On Mon, Aug 18, 2008 at 12:15 PM, Dustin Kirkland
<dustin.kirkland at gmail.com> wrote:
> On Mon, Aug 18, 2008 at 5:33 PM, Serge Hallyn <serge.hallyn at gmail.com> wrote:
>> Please let me know when this is in your test kernel repo
>> (deb http://ppa.launchpad.net/timg-tpi/ubuntu hardy main)  and I will give it a
>> shot.
>
> Serge-
>
> You should be able to test Tim's test kernel at:
>  * https://launchpad.net/~timg-tpi/+archive
>
> linux - 2.6.24-22.41ubuntu1
>
> :-Dustin
>
> --
> Hardy ecryptfs can cause data loss
> https://bugs.launchpad.net/bugs/242448
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: Unknown
> Status in "linux" source package in Ubuntu: Confirmed
> Status in linux in Ubuntu Hardy: Fix Committed
>
> Bug description:
> This bug can cause data loss on an ecryptfs mounted filesystem.
>
> The test case looks like this:
>
> # mkdir /tmp/dir1 /tmp/dir2
> # mount -t ecryptfs /tmp/dir1 /tmp/dir2
> (any ecryptfs mount options are fine, choose defaults)
> # cp /usr/share/common-licenses/GPL-3 /tmp/dir2
> # umount /tmp/dir2
> # mount -t ecryptfs /tmp/dir1 /tmp/dir2
> (choose same options/passphrase as last mount)
> # echo foo >> /tmp/dir2/GPL-3
> # tail /tmp/dir2/GPL-3
> # reset
>
> You will see badly decrypted data printed to screen, whereas you should see the GPLv3 plus "foo" printed to screen.  The data in this file is permanently hosed.
>
> The fix for this bug was applied upstream against 2.6.26, and is already in the intrepid kernel.
>
> The git commit diff can be seen here:
>  * http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commitdiff;h=d3e49afbb66109613c3474f2273f5830ac2dcb09
>
> I will gladly test a new Hardy kernel as soon as it becomes available.
>
> :-Dustin
>

-- 
Hardy ecryptfs can cause data loss
https://bugs.launchpad.net/bugs/242448
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.