diff options
author | 2010-12-20 16:21:11 +0800 | |
---|---|---|
committer | 2010-12-22 18:34:42 -0800 | |
commit | 1e6d9153df27923649976554d034a69ac7b28f95 (patch) | |
tree | dfb165957114d9cd6afd1ddbc316ff65d001bed1 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | ocfs2/cluster: Pin the local node when o2hb thread starts (diff) | |
download | wireguard-linux-1e6d9153df27923649976554d034a69ac7b28f95.tar.xz wireguard-linux-1e6d9153df27923649976554d034a69ac7b28f95.zip |
ocfs2: Release buffer_head in case of error in ocfs2_double_lock.
In ocfs2_double_lock, when ocfs2_inode_lock for inode1 fails, we
just unlock inode2 and return without releasing buffer we get from
inode_lock(inode2). The good thing is that it is freed by the only
caller ocfs2_rename when it exits.
But I don't think this is a right way for error handling. We should
free the buffer_head we get in ocfs2_double_lock before exit so that
the caller doesn't need to take care of it.
Signed-off-by: Tao Ma <boyu.mt@taobao.com>
Signed-off-by: Joel Becker <joel.becker@oracle.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions