ext4: move_extent code cleanup
authorDmitry Monakhov <dmonakhov@openvz.org>
Wed, 26 Sep 2012 16:32:19 +0000 (12:32 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Wed, 26 Sep 2012 16:32:19 +0000 (12:32 -0400)
commit03bd8b9b896c8e940f282f540e6b4de90d666b7c
tree76e770537d52af02d3664c296560b3d0d708ab39
parent0acdb8876fead922c9ffa6768c5675a37485c48c
ext4: move_extent code cleanup

- Remove usless checks, because it is too late to check that inode != NULL
  at the moment it was referenced several times.
- Double lock routines looks very ugly and locking ordering relays on
  order of i_ino, but other kernel code rely on order of pointers.
  Let's make them simple and clean.
- check that inodes belongs to the same SB as soon as possible.

Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@vger.kernel.org
fs/ext4/move_extent.c