As the current bug is fixed, I have opened a new bug to address this
issue specifically.
Please post further comments to Bug #357345.
:-Dustin
--
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you
Ext4
grtz
Bert
--
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
bert-
What is the underlying filesystem? ext3? ext4?
:-Dustin
--
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I still get these error messages. All updates are applied on my system.
[ 6643.280765] ecryptfs_parse_tag_70_packet: max_packet_size is [56]; real
packet size is [51]
[ 6643.280772] ecryptfs_decode_and_decrypt_filename: Could not parse tag 70
packet from filename; copying through filename as-is
Thanks İsmail - I've tried quite a bit and have been unsuccessful in
reproducing these messages on my system. If Dustin or İsmail can
provide me with an encrypted filename that triggers these messages, I
will fix the problem.
Currently, the best way to do this would be to single out which
plainte
This bug is closedb but with latest Jaunty packages dmesg still shows:
[ 2028.376354] ecryptfs_parse_tag_70_packet: max_packet_size is [56]; real
packet size is [51]
[ 2028.376357] ecryptfs_decode_and_decrypt_filename: Could not parse tag 70
packet from filename; copying through filename as-is
[
** Changed in: ecryptfs-utils (Ubuntu)
Status: Triaged => Fix Released
--
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Dustin - I am in agreement with Tim. Sorry I didn't respond quicker.
--
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Good, thanks, Tim.
:-Dustin
--
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Dustin - other then a couple of system wide commits (vfs creds and some
current user macros), I see no substantive difference between Jaunty
fs/ecryptfs and the version in Linus tree as of 2.6.29-rc8
a1e4ee22863d41a6fbb24310d7951836cb6dafe7.
** Changed in: linux (Ubuntu)
Status: Confirmed =
Tyler/Tim-
What's our current status here? I don't think Tim has sync'd the
ecryptfs kernel code for Jaunty.
Tyler-
What's your recommendation for ecryptfs git commits that should be
sync'd from 2.6.29 to Ubuntu's 2.6.28?
:-Dustin
--
please sync jaunty ecryptfs kernel module with linus' git
Tim-
I'm actually suffering from the EXT4 zero-byte-file bug, Bug #317781.
I've added a few comments to that effect.
:-Dustin
--
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you are a member of
Hi Tim - I agree that the vfs_fsync patch is the only one of much
interest, but it isn't the cause of Dustin's problems. We have been
working together to determine the problem and figured out that he had
some non-eCryptfs files in his lower mount point. This is due to a
problem where creates can
I compared the commits to Jaunty ecryptfs versus 2.6.29-rc7 and found
these differences (e.g. ecryptfs commits missing in Jaunty):
fs/Kconfig: move ecryptfs out
add a vfs_fsync helper
inode->i_op is never NULL
CRED: Pass credentials through dentry_open()
CRED: Wrap task credential accesses in the
On Thu, Mar 5, 2009 at 3:27 PM, Tyler Hicks wrote:
> I made a quick list of the commit difference between the current jaunty
> and 2.6.29-rc7 git trees. Unfortunately, several of these patches touch
> quite a bit more than eCryptfs code.
>
> Missing from jaunty kernel:
> ---
> 745ca2475a6ac596e3d
I made a quick list of the commit difference between the current jaunty
and 2.6.29-rc7 git trees. Unfortunately, several of these patches touch
quite a bit more than eCryptfs code.
Missing from jaunty kernel:
---
745ca2475a6ac596e3d8d37c2759c0fbe2586227
4c728ef583b3d82266584da5cb068294c09df31e
** Attachment added: "ecryptfs.patch"
http://launchpadlibrarian.net/22810547/ecryptfs.patch
** Also affects: ecryptfs-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Tim Gardner (timg-tp
17 matches
Mail list logo
