[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 2.6.32-43.97 --- linux (2.6.32-43.97) lucid-proposed; urgency=low [Luis Henriques] * Release Tracking Bug - LP: #1045405 [ Upstream Kernel Changes ] * rds: set correct msg_namelen - LP: #1031112 - CVE-2012-3430 * eCryp

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 2.6.38-16.67 --- linux (2.6.38-16.67) natty-proposed; urgency=low [Luis Henriques] * Release Tracking Bug - LP: #1045383 [ Upstream Kernel Changes ] * rds: set correct msg_namelen - LP: #1031112 - CVE-2012-3430 * eCryp

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-10 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/lucid-proposed/linux-lts-backport-natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should initialize existing empty files at open() To manage n

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-10 Thread Colin King
Tested on Natty -proposed: Linux ubuntu 2.6.38-16-server #67-Ubuntu SMP Thu Sep 6 18:15:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux sudo ./tests/run_tests.sh -K -c destructive -b 100 -D /tmp/image -l /lower -u /upper -t lp-911507.sh -f ext2,ext3,ext4,xfs,btrfs Running eCryptfs filesystem tests

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-10 Thread Luis Henriques
This bug is awaiting verification that the kernel for Natty in -proposed solves the problem (2.6.38-16.67). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-natty' to 'verification-done-natty'. If verification is not done by

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-07 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should initialize existing empty files at open() To manage notifications ab

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-07 Thread rakkenes
I also have 12.04 and see many errors like these: Sep 7 21:53:01 CCCx kernel: [ 1031.641254] Either the lower file is not in a valid eCryptfs format, or the key could not be r etrieved. Plaintext passthrough mode is not enabled; returning -EIO Sep 7 21:53:01 CCCux kernel: [ 1031.641340] Valid e

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-07 Thread Colin King
Tested on Lucid Linux ubuntu 2.6.32-43-server #97-Ubuntu SMP Wed Sep 5 16:56:41 UTC 2012 x86_64 GNU/Linux sudo ./tests/run_tests.sh -K -c safe -b 100 -D /tmp/image -l /lower -u /upper -t lp-911507.sh -f ext2,ext3,ext4,xfs,btrfs Running eCryptfs filesystem tests on ext2 lp-911507

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-05 Thread John John Doe
I faced this error on Ubuntu 12.04. on my encrypted home partition. I noticed it when I tried to backup files with rsync. Also Firefox was broken somewhat. It could no longer load any bookmarks. I also had a full hard disc before which might have caused the problem. Now rsync seems to work - but th

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.0.0-25.41 --- linux (3.0.0-25.41) oneiric-proposed; urgency=low [Luis Henriques] * Release Tracking Bug - LP: #1036178 [ Andy Whitcroft ] * SAUCE: rds_ib_send() -- prevent local pings triggering BUG_ON() - LP: #1016299

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-09-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.2.0-30.48 --- linux (3.2.0-30.48) precise-proposed; urgency=low [Luis Henriques] * Release Tracking Bug - LP: #1041217 [ Upstream Kernel Changes ] * mutex: Place lock in contended state after fastpath_lock failure - LP: #1

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-22 Thread Tim Gardner
** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Natty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Lucid) Assignee: (unassign

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-21 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/precise-proposed/linux-armadaxp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should initialize existing empty files at open() To manage notificat

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-21 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/oneiric-proposed/linux-ti-omap4 ** Branch linked: lp:ubuntu/precise-proposed/linux-ti-omap4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should i

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-21 Thread Colin King
Tested using lp:~colin-king/ecryptfs/test-fixes with ext2, ext3, ext4, xfs and btrfs lower file system, Linux ubuntu 3.2.0-30-generic #47-Ubuntu SMP Wed Aug 15 19:30:10 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux sudo ./tests/run_tests.sh -K -c safe -b 100 -D /tmp/image -l /lower -u /upper -t lp-

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-21 Thread Colin King
Tested using lp:~colin-king/ecryptfs/test-fixes with ext2, ext3, ext4, xfs and btrfs lower file system, Linux ubuntu 3.0.0-25-server #41-Ubuntu SMP Mon Aug 13 18:18:27 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux sudo ./tests/run_tests.sh -K -c safe -b 100 -D /tmp/image -l /lower -u /upper -t lp-9

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-21 Thread Luis Henriques
This bug is awaiting verification that the kernel for Precise in -proposed solves the problem (3.2.0-30.47). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-precise' to 'verification-done-precise'. If verification is not do

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-20 Thread Brad Figg
** Tags added: verification-needed-oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should initialize existing empty files at open() To manage notifications about this b

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-09 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/linux-lowlatency -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should initialize existing empty files at open() To manage notifications about this

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-09 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.5.0-9.9 --- linux (3.5.0-9.9) quantal-proposed; urgency=low [ Daniel P. Berrange ] * SAUCE: (drop after 3.6) Forbid invocation of kexec_load() outside initial PID namespace - LP: #1034125 [ Douglas Bagnall ] * SAUCE: Unloc

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-08 Thread Tim Gardner
** Changed in: linux (Ubuntu Oneiric) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Precise) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-07 Thread Tim Gardner
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin King (colin-king) ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Un

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-03 Thread Tyler Hicks
** Changed in: ecryptfs Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should initialize existing empty files at open() To manage

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-02 Thread Tyler Hicks
This fix was merged into Linus' tree. It should be released in 3.6-rc1. http://git.kernel.org/linus/e3ccaa9761200952cc269b1f4b7d7bb77a5e071b ** Changed in: ecryptfs Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-08-02 Thread Christian Mertes
FĂ©lim Whiteley, did you read the other bugs before marking them as duplicates? Bug #957843 is about data loss (and none of the devs seems to care -- man am I happy I left ecryptfs for good), whereas in this bug people are discussing whether this or that fix might or might not result in data loss. T

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-07-31 Thread Shevek
.skype/shared.xml for me too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911507 Title: eCryptfs should initialize existing empty files at open() To manage notifications about this bug go to: http

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-07-31 Thread Marius Kotsbak
** Description changed: Empty files left in the lower filesystem cause eCryptfs to return error codes and log error messages when eCryptfs tries to read the metadata. This has been the mode of operation since the beginning of eCryptfs. There is no eCryptfs metadata available, so it seemed

[Bug 911507] Re: eCryptfs should initialize existing empty files at open()

2012-07-31 Thread Marius Kotsbak
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: precise ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.n