summaryrefslogtreecommitdiffstats
path: root/fs/ecryptfs/kthread.c
diff options
context:
space:
mode:
authorTyler Hicks <tyhicks@canonical.com>2012-01-18 18:30:04 -0600
committerTyler Hicks <tyhicks@canonical.com>2012-01-25 14:43:40 -0600
commit5e6f0d769017cc49207ef56996e42363ec26c1f0 (patch)
tree1cfcfdaeda81e1d17725bdd1e1a964cc5a0b40b5 /fs/ecryptfs/kthread.c
parent684a3ff7e69acc7c678d1a1394fe9e757993fd34 (diff)
eCryptfs: Make truncate path killable
ecryptfs_write() handles the truncation of eCryptfs inodes. It grabs a page, zeroes out the appropriate portions, and then encrypts the page before writing it to the lower filesystem. It was unkillable and due to the lack of sparse file support could result in tying up a large portion of system resources, while encrypting pages of zeros, with no way for the truncate operation to be stopped from userspace. This patch adds the ability for ecryptfs_write() to detect a pending fatal signal and return as gracefully as possible. The intent is to leave the lower file in a useable state, while still allowing a user to break out of the encryption loop. If a pending fatal signal is detected, the eCryptfs inode size is updated to reflect the modified inode size and then -EINTR is returned. Signed-off-by: Tyler Hicks <tyhicks@canonical.com> Cc: <stable@vger.kernel.org>
Diffstat (limited to 'fs/ecryptfs/kthread.c')
0 files changed, 0 insertions, 0 deletions