eCryptfs: Make truncate path killable
Bug #947270 reported by
Colin Ian King
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Colin Ian King | ||
Natty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Natty SRU:
SRU justification:
Impact:
ecryptfs_write() does not detect a pending fatal signal which means
write operations cannot be interrupted which is problematic when
truncating a file to several GB as one has to wait for this operation
to complete.
Fix:
Upstream commit 5e6f0d769017cc4
Testcase:
Truncating a non-existent file to several GB and sending it
SIGINT will not respond until complete which can take a long
time on a slow device. With this fix, SIGINT is far more
responsive as expected.
Related branches
Changed in linux (Ubuntu): | |
assignee: | nobody → Colin King (colin-king) |
Changed in linux (Ubuntu Natty): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 947270
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.