aboutsummaryrefslogtreecommitdiffstats
path: root/sound
diff options
context:
space:
mode:
authorTyler Hicks <tyhicks@canonical.com>2014-10-07 15:51:55 -0500
committerBen Hutchings <ben@decadent.org.uk>2015-02-20 00:49:22 +0000
commite340a90b13694d8051e37cc6e2e06f6aedcd8051 (patch)
tree75932bd9ab8abe5f5c5edc77ccb2f9cf84f914c6 /sound
parentac4619ec85e120ecbcd8c96e518cd99aa41c8012 (diff)
downloadkernel_samsung_smdk4412-e340a90b13694d8051e37cc6e2e06f6aedcd8051.zip
kernel_samsung_smdk4412-e340a90b13694d8051e37cc6e2e06f6aedcd8051.tar.gz
kernel_samsung_smdk4412-e340a90b13694d8051e37cc6e2e06f6aedcd8051.tar.bz2
eCryptfs: Force RO mount when encrypted view is enabled
commit 332b122d39c9cbff8b799007a825d94b2e7c12f2 upstream. The ecryptfs_encrypted_view mount option greatly changes the functionality of an eCryptfs mount. Instead of encrypting and decrypting lower files, it provides a unified view of the encrypted files in the lower filesystem. The presence of the ecryptfs_encrypted_view mount option is intended to force a read-only mount and modifying files is not supported when the feature is in use. See the following commit for more information: e77a56d [PATCH] eCryptfs: Encrypted passthrough This patch forces the mount to be read-only when the ecryptfs_encrypted_view mount option is specified by setting the MS_RDONLY flag on the superblock. Additionally, this patch removes some broken logic in ecryptfs_open() that attempted to prevent modifications of files when the encrypted view feature was in use. The check in ecryptfs_open() was not sufficient to prevent file modifications using system calls that do not operate on a file descriptor. Signed-off-by: Tyler Hicks <tyhicks@canonical.com> Reported-by: Priya Bansal <p.bansal@samsung.com> [bwh: Backported to 3.2: adjust context] Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions