eCryptfs: Unlock page in write_begin error path
authorTyler Hicks <tyhicks@linux.vnet.ibm.com>
Wed, 9 Mar 2011 17:49:13 +0000 (11:49 -0600)
committerBrad Figg <brad.figg@canonical.com>
Wed, 27 Apr 2011 18:40:31 +0000 (11:40 -0700)
commita4fcd996a302d08b7c124e03a99513c01b1bface
tree81f21ec318f21506f62a5ae449d9fc2d519bebd3
parent4021d60d2916dacb434e07dcbf262cd858659759
eCryptfs: Unlock page in write_begin error path

BugLink: http://bugs.launchpad.net/bugs/761134

commit 50f198ae16ac66508d4b8d5a40967a8507ad19ee upstream.

Unlock the page in error path of ecryptfs_write_begin(). This may
happen, for example, if decryption fails while bring the page
up-to-date.

Signed-off-by: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
fs/ecryptfs/mmap.c