linux-toradex.git/fs/ecryptfs/read_write.c, branch v4.5-rc3

ecryptfs: don't open-code kernel_read()

2013-05-09T17:39:58+00:00

Signed-off-by: Al Viro

export kernel_write(), convert open-coded instances

2013-02-26T07:46:11+00:00

Signed-off-by: Al Viro

ecryptfs: remove the second argument of k[un]map_atomic()

2012-02-16T22:06:27+00:00

Signed-off-by: Cong Wang 
Signed-off-by: Tyler Hicks

eCryptfs: Remove unused ecryptfs_read()

2012-01-25T20:43:41+00:00

ecryptfs_read() has been ifdef'ed out for years now and it was
apparently unused before then. It is time to get rid of it for good.

Signed-off-by: Tyler Hicks

eCryptfs: Make truncate path killable

2012-01-25T20:43:40+00:00

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 
Cc:

eCryptfs: Infinite loop due to overflow in ecryptfs_write()

2012-01-25T20:43:40+00:00

ecryptfs_write() can enter an infinite loop when truncating a file to a
size larger than 4G. This only happens on architectures where size_t is
represented by 32 bits.

This was caused by a size_t overflow due to it incorrectly being used to
store the result of a calculation which uses potentially large values of
type loff_t.

[tyhicks@canonical.com: rewrite subject and commit message]
Signed-off-by: Li Wang 
Signed-off-by: Yunchuan Wen 
Reviewed-by: Cong Wang 
Cc: 
Signed-off-by: Tyler Hicks

eCryptfs: Return error when lower file pointer is NULL

2011-08-09T18:42:45+00:00

When an eCryptfs inode's lower file has been closed, and the pointer has
been set to NULL, return an error when trying to do a lower read or
write rather than calling BUG().

https://bugzilla.kernel.org/show_bug.cgi?id=37292

Signed-off-by: Tyler Hicks 
Cc:

ecryptfs: modify write path to encrypt page in writepage

2011-03-28T06:47:45+00:00

Change the write path to encrypt the data only when the page is written to
disk in ecryptfs_writepage. Previously, ecryptfs encrypts the page in
ecryptfs_write_end which means that if there are multiple write requests to
the same page, ecryptfs ends up re-encrypting that page over and over again.
This patch minimizes the number of encryptions needed.

Signed-off-by: Thieu Le 
[tyhicks: Changed NULL .drop_inode sop pointer to generic_drop_inode]
Signed-off-by: Tyler Hicks

switch ecryptfs_write() to struct inode *, kill on-stack fake files

2010-05-21T22:31:28+00:00

Signed-off-by: Al Viro

switch ecryptfs_get_locked_page() to struct inode *

2010-05-21T22:31:28+00:00

Signed-off-by: Al Viro