summaryrefslogtreecommitdiffstats
path: root/fs/jfs/endian24.h
diff options
context:
space:
mode:
authorEvgeniy Dushistov <dushistov@mail.ru>2006-06-05 08:21:03 -0500
committerDave Kleikamp <shaggy@austin.ibm.com>2006-06-05 08:21:03 -0500
commit48ce8b056c88920c8ac187781048f5dae33c81b9 (patch)
treed03665af62302a252a5c60e7a920190ed93cbec8 /fs/jfs/endian24.h
parent672c6108a51bf559d19595d9f8193dfd81f0f752 (diff)
downloadop-kernel-dev-48ce8b056c88920c8ac187781048f5dae33c81b9.zip
op-kernel-dev-48ce8b056c88920c8ac187781048f5dae33c81b9.tar.gz
JFS: commit_mutex cleanups
I look at code, and see that 1)locks wasn't release in the opposite order in which they were taken 2)in jfs_rename we lock new_ip, and in "error path" we didn't unlock it 3)I see strange expression: "! !" May be this worth to fix? Signed-off-by: Evgeniy Dushistov <dushistov@mail.ru> Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
Diffstat (limited to 'fs/jfs/endian24.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud