ecryptfs_truncate should not call vmtruncate on lower inode
Bug #451368 reported by
Tyler Hicks
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Fix Released
|
High
|
Tyler Hicks | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Colin Ian King |
Bug Description
From Christoph Hellwig:
"It looks like ecryptfs calls vmtruncate directly on the lower filesystem, which is quite wrong. Vmtruncate is only a helper for the filesystem, and while most filesystems end up calling vmtruncate from their ->setattr implementation if ATTR_SIZE is set there are many that require additional work. I think ecryptfs needs to got through notify_change() / ->setattr if it wants truncate to work reliably and without silent corruption or leaking blocks on a variety of filesystems."
See entire thread here:
Changed in ecryptfs: | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Lucid): | |
status: | New → Fix Committed |
To post a comment you must log in.
Patch submitted for review: article. gmane.org/ gmane.linux. file-systems/ 36107
http://
Has been applied to: kernel. org/pub/ scm/linux/ kernel/ git/ecryptfs/ ecryptfs- 2.6.git# next
git://git.