ecryptfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: Henry Jensen <hjensen@gmx.de>, Kenneth Tan <gmane@way-of-the-blade.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Can't list directories with kernel 4.4.14 and ecryptfs
Date: Tue, 28 Jun 2016 23:36:23 -0500	[thread overview]
Message-ID: <57735047.1050706@canonical.com> (raw)
In-Reply-To: <5771AD13.2010408@canonical.com>


[-- Attachment #1.1: Type: text/plain, Size: 1602 bytes --]

On 06/27/2016 05:47 PM, Tyler Hicks wrote:
> On 06/27/2016 04:21 PM, Henry Jensen wrote:
>> Hi Tyler,
>>
>> Am 27. Juni 2016 21:19:08 MESZ, schrieb Tyler Hicks <tyhicks@canonical.com>:
>>> On 06/27/2016 11:27 AM, Henry Jensen wrote:
>>>> Greetings,
>>>>
>>>> I'm using ecryptfs with Slackware current and kernel 4.4.14. In
>>> kernel
>>>> 4.4.14 was a patch introduced which make it impossilble to list the
>>>> contents of a directory.[0]
>>>>
>>>> The mount itself works, but listing a directory results in an error
>>>> "wrong medium type". Showing the contents and the file itself
>>> (presumed
>>>> the name of the file is known) works.
>>>
>>> Hi Henry - sorry for the trouble. What filesystem are you mounting
>>> eCryptfs on top of?
>>
>>
>> I use ext4. With 'ecryptfs-mount-private' $HOME/.Private is mounted on $HOME/Private. 
>>
>> ecryptfs worked perfectly until I upgraded to kernel 4.4.14. I tested it on another machine with Slackware64 and a 64bit kernel now - same result.
> 
> Thanks. The backported version of the patch needs to be adjusted. I'll
> try to get a patch out the stable list tomorrow.

I've sent a fix to the stable list (and cc'ed the ecryptfs list). I
tested on 4.4.y and 3.18.y on ext{2,3,4}, btrfs, and xfs. It should fix
the regression that you hit.

Tyler

> 
> Tyler
> 
>>
>> Regards,
>> Henry
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-06-29  4:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 16:27 Can't list directories with kernel 4.4.14 and ecryptfs Henry Jensen
2016-06-27 19:19 ` Tyler Hicks
2016-06-27 21:21   ` Henry Jensen
2016-06-27 22:46     ` Kenneth Tan
2016-06-27 22:47     ` Tyler Hicks
2016-06-29  4:36       ` Tyler Hicks [this message]
2016-07-01 20:15         ` Henry Jensen
2016-07-01 21:06           ` Tyler Hicks
2016-07-01 21:16             ` Henry Jensen
2016-07-01 21:33               ` Tyler Hicks
2016-07-01 21:49               ` Henry Jensen

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=57735047.1050706@canonical.com \
    --to=tyhicks@canonical.com \
    --cc=ecryptfs@vger.kernel.org \
    --cc=gmane@way-of-the-blade.com \
    --cc=hjensen@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).