← Back to team overview

ecryptfs team mailing list archive

Re: [Bug 380073] Re: Error reading symlinks in an ecryptfs filesystem

 

Hi, thanks for checking.

Personally, I can live with using some karmic packages on my desktop system.
So calling it critical might be a bit too much.
I reverted to full disk encryption in the mean time.


On Fri, Jul 24, 2009 at 10:39 PM, Dustin
Kirkland<dustin.kirkland@xxxxxxxxx> wrote:
> I can confirm this on Jaunty 2.6.28-13
>
> However this is fixed upstream.  I cannot reproduce it on karmic's
> 2.6.31-3 kernel.
>
> If you really think this is a critical issue for jaunty, we can perhaps
> try to update jaunty's kernel.  I'm not sure I can make that case,
> though.
>
> :-Dustin
>
> ** Changed in: ecryptfs
>       Status: New => Confirmed
>
> ** Changed in: ecryptfs-utils (Ubuntu)
>       Status: New => Confirmed
>
> ** Changed in: ecryptfs
>       Status: Confirmed => Fix Released
>
> ** Changed in: ecryptfs-utils (Ubuntu)
>       Status: Confirmed => Fix Released
>
> --
> Error reading symlinks in an ecryptfs filesystem
> https://bugs.launchpad.net/bugs/380073
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
Error reading symlinks in an ecryptfs filesystem
https://bugs.launchpad.net/bugs/380073
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in eCryptfs - Enterprise Cryptographic Filesystem: Fix Released
Status in “ecryptfs-utils” package in Ubuntu: Fix Released

Bug description:
Binary package hint: libecryptfs0

The problem shows up in Git, though I don't think it is a Git problem (though I could be wrong). The issue is that when Git tries to read a symlink on an eCryptfs filesystem, it fails with:

error: readlink("link-to-file"): Invalid argument
error: unable to index file link-to-file

I can confirm that it works on my ext4 root partition, and it has worked in the past, so I'm fairly sure it is an eCryptfs issue.

I have attached a script which demonstrates the problem. It creates a folder "test" in the current directory, initiates a git repository, adds a file and a link to that file. Here is what the output looks like for me:

(/ is an ext4 partition and my home folder is eCryptfs)

  $ cd /tmp
  $ sh ~/test-script.sh

    Initialized empty Git repository in /tmp/test/.git/
    Created initial commit f35f3e0: Commit file
     1 files changed, 1 insertions(+), 0 deletions(-)
     create mode 100644 file
    Created commit 3ffda66: commit link
     1 files changed, 1 insertions(+), 0 deletions(-)
     create mode 120000 link-to-file

  $ cd ~/
  $ sh ~/test-script.sh

    Created initial commit 070bd2f: Commit file
     1 files changed, 1 insertions(+), 0 deletions(-)
     create mode 100644 file
    error: readlink("link-to-file"): Invalid argument
    error: unable to index file link-to-file
    fatal: adding files failed
    # On branch master
    # Untracked files:
    #   (use "git add <file>..." to include in what will be committed)
    #
    #       link-to-file
    nothing added to commit but untracked files present (use "git add" to track)

Some system info:

  $ uname -a
    Linux priscilla 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

  $ cat /etc/issue
    Ubuntu 9.04 \n \l



References