From: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
To: Roberto Oppedisano <roberto.oppedisano@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
ecryptfs-devel@lists.launchpad.net,
ecryptfs-users@lists.launchpad.net
Subject: Re: regression: ecryptfs broken on 2.6.36-rc2 (x86_64)
Date: Fri, 27 Aug 2010 15:22:50 -0500 [thread overview]
Message-ID: <20100827202249.GA23972@boomer> (raw)
In-Reply-To: <4C735DC7.7090308@gmail.com>
On Tue Aug 24, 2010 at 07:51:03AM +0200, Roberto Oppedisano <roberto.oppedisano@gmail.com> wrote:
> I'm having the very same problem reported from another ecryptfs user.
>
> https://bugs.launchpad.net/ecryptfs/+bug/623087
>
> In short permissions seem to be broken on ecryptfs mounts, and ls
> output looks like:
>
> ls: cannot access enctest/file1: No such file or directory
> ls: cannot access enctest/sub: No such file or directory
> total 12
> 545077 -????????? ? ? ? ? ? file1
> 545075 -rw-r--r-- 1 root root 3 2010-08-24 08:53 file3-2.6.36
> 545078 d????????? ? ? ? ? ? sub
>
> Everything was fine in 2.6.35.
>
A fix for this regression should be merged by 2.6.36-rc3. Until then,
you can get the patch from:
http://git.kernel.org/?p=linux/kernel/git/ecryptfs/ecryptfs-2.6.git;a=commit;h=93c3fe40c279f002906ad14584c30671097d4394
For those interested, the bug report linked above has a description
of the problem. In general, you shouldn't use eCryptfs in 2.6.36-rc{1,2}
if you have file name encryption enabled.
Tyler
prev parent reply other threads:[~2010-08-27 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 5:51 regression: ecryptfs broken on 2.6.36-rc2 (x86_64) Roberto Oppedisano
2010-08-27 20:22 ` Tyler Hicks [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100827202249.GA23972@boomer \
--to=tyhicks@linux.vnet.ibm.com \
--cc=ecryptfs-devel@lists.launchpad.net \
--cc=ecryptfs-users@lists.launchpad.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.oppedisano@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.