Sure. But maybe we need to take more time since he is recently very
busy. If this bug doesn't have much affect on you, we could wait.
Otherwise, you can test it and apply it in your kernel. After all, it
can solve your problem though it may not be the best way.
--
You received this bug
Hi Jason, thanks for taking this. I'm happy to test in the coming week
or so, we also need to get Tyler's thoughts since he's going to need to
sign off too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1612492
Title:
remounting breaks size reporting and rsync
Status in eCryptfs:
In Progress
Status in
Hello Benjamin Gemmill,
I'm done with the patch (see the attachment). It can be applied in the
latest linus' tree and 4.8.17 kernel.If you have any idea or advice,
please tell me. Thanks.
** Patch added: "0001-ecryptfs-Fix-stat-command-displays-wrong-file-size.patch"
I tested different kernels and two filesystem (xfs and ext4). It turns
out that we cannot read less than value_size (which is 81 in ecryptfs)
buffer when doing ecryptfs_read_and_validate_xattr_region(). In
ecryptfs_read_and_validate_xattr_region() function, "file_size" array is
the buffer we're
I'm working on this bug issue, so I reassign to me. The maintainers of
eCryptfs are very busy, if they want to write the patch, that would be
great!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tyler, if you are writing the patch, please tell me, I will assign it to
you.
** Changed in: ecryptfs
Assignee: Tyler Hicks (tyhicks) => Jason Xing (wlxing)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also verified in 3.3.8
I compile the kernel (3.3.8) on Ubuntu 14.04 and Centos 7-1511.
After I mount ecryptfs with ecryptfs_xattr option, it will terminate if
I copy some file in it. First time I copy files, it will be killed. Next
time I copy files, it will hang and do nothing.
Test outputs:
$
It also affects me. I tested it on 14.04 (64-bit) and 16.04 (64-bit).
Verified in 4.2.0-27-generic and 4.8.0-36-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1612492
Title:
The bug is in ecryptfs_read_and_validate_xattr_region(). It calls
ecryptfs_getxattr_lower(), which is returning -34 (ERANGE). With
ecryptfs_getxattr_lower() failing, it means that we can't retrieve the
proper file size from the xattr metadata and can't set an an accurate
value in the kstat buffer.
Hi Tyler, thanks for commenting on this.
I'm trying to get encryptfs going over a remote filesystem, and xattrs are the
only practical place to put crypto headers due to file reading speeds:
https://www.amazon.com/clouddrive/
And in particular, if you go to read any part of a file, you have to
Yes, it is caused by the ecryptfs_xattr_metadata option. A workaround
would be to not store the crypto metadata in the xattr and use the
default of storing the metadata in the file contents.
The ecryptfs_xattr_metadata option is not the default and, therefore, is
not as widely used/tested. This
Verified in 4.8-rc2.
** Changed in: ecryptfs
Status: New => Confirmed
** Changed in: ecryptfs
Importance: Undecided => Medium
** Changed in: ecryptfs-utils
Status: New => Invalid
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance:
13 matches
Mail list logo
