Jan Kara 9a6ce27a5d fs: no need to check source
commit 66d8fc0539b0d49941f313c9509a8384e4245ac1 upstream.

The @source inode must be valid. It is even checked via IS_SWAPFILE()
above making it pretty clear. So no need to check it when we unlock.

What doesn't need to exist is the @target inode. The lock_two_inodes()
helper currently swaps the @inode1 and @inode2 arguments if @inode1 is
NULL to have consistent lock class usage. However, we know that at least
for vfs_rename() that @inode1 is @source and thus is never NULL as per
above. We also know that @source is a different inode than @target as
that is checked right at the beginning of vfs_rename(). So we know that
@source is valid and locked and that @target is locked. So drop the
check whether @source is non-NULL.

Fixes: 28eceeda130f ("fs: Lock moved directories")
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
Closes: https://lore.kernel.org/r/202307030026.9sE2pk2x-lkp@intel.com
Message-Id: <20230703-vfs-rename-source-v1-1-37eebb29b65b@kernel.org>
[brauner: use commit message from patch I sent concurrently]
Signed-off-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2023-07-27 08:37:26 +02:00
..
2023-06-21 15:44:12 +02:00
2021-09-22 12:26:25 +02:00
2023-07-27 08:37:03 +02:00
2022-06-14 18:11:36 +02:00
2023-07-27 08:37:06 +02:00
2023-02-22 12:50:35 +01:00
2022-06-14 18:11:41 +02:00
2020-10-01 13:17:19 +02:00
2019-12-17 19:55:30 +01:00
2023-07-27 08:37:26 +02:00
2023-01-18 11:41:44 +01:00