ACK: [Natty][SRU][PATCH 0/1] eCryptfs: Make truncate path killable

[Tim Gardner]

On 03/05/2012 09:48 AM, Colin King wrote:
> From: Colin Ian King<colin.king at canonical.com>
>
> BugLink: http://bugs.launchpad.net/bugs/947270
>
> 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 5e6f0d769017cc49207ef56996e42363ec26c1f0
>
> 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.
>
> Note:
>
> This patch has already been sent to stable and has been applied
> to Lucid but was ommitted for Natty.
>
> Li Wang (1):
>    eCryptfs: Infinite loop due to overflow in ecryptfs_write()
>
>   fs/ecryptfs/read_write.c |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>


-- 
Tim Gardner tim.gardner at canonical.com