diff options
| author | Joseph Qi <joseph.qi@huawei.com> | 2013-05-24 15:55:34 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-06-07 12:46:36 -0700 |
| commit | 70d53e5acf842b00efe048846aaf49d1f664b23d (patch) | |
| tree | 3e2400501037913c4886c3dd69f5467a2a411276 /arch/arm | |
| parent | 2b90057252cfde394556c989a0eb740ed6734389 (diff) | |
| download | kernel_samsung_smdk4412-70d53e5acf842b00efe048846aaf49d1f664b23d.zip kernel_samsung_smdk4412-70d53e5acf842b00efe048846aaf49d1f664b23d.tar.gz kernel_samsung_smdk4412-70d53e5acf842b00efe048846aaf49d1f664b23d.tar.bz2 | |
ocfs2: goto out_unlock if ocfs2_get_clusters_nocache() failed in ocfs2_fiemap()
commit b4ca2b4b577c3530e34dcfaafccb2cc680ce95d1 upstream.
Last time we found there is lock/unlock bug in ocfs2_file_aio_write, and
then we did a thorough search for all lock resources in
ocfs2_inode_info, including rw, inode and open lockres and found this
bug. My kernel version is 3.0.13, and it is also in the lastest version
3.9. In ocfs2_fiemap, once ocfs2_get_clusters_nocache failed, it should
goto out_unlock instead of out, because we need release buffer head, up
read alloc sem and unlock inode.
Signed-off-by: Joseph Qi <joseph.qi@huawei.com>
Reviewed-by: Jie Liu <jeff.liu@oracle.com>
Cc: Mark Fasheh <mfasheh@suse.com>
Cc: Joel Becker <jlbec@evilplan.org>
Acked-by: Sunil Mushran <sunil.mushran@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/arm')
0 files changed, 0 insertions, 0 deletions