writeback: Protect inode->i_io_list with inode->i_lock
authorJan Kara <jack@suse.cz>
Wed, 10 Jun 2020 15:36:03 +0000 (17:36 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 3 Sep 2020 09:22:32 +0000 (11:22 +0200)
commit0fa1f08619ccc5a7a59c9ebd7375c4b0ba688b67
tree178659dfc86028727e9fbeb022afc6d56da293ba
parent5026ce65aacbf009f3bc9e51f66c98fa936bdf88
writeback: Protect inode->i_io_list with inode->i_lock

commit b35250c0816c7cf7d0a8de92f5fafb6a7508a708 upstream.

Currently, operations on inode->i_io_list are protected by
wb->list_lock. In the following patches we'll need to maintain
consistency between inode->i_state and inode->i_io_list so change the
code so that inode->i_lock protects also all inode's i_io_list handling.

Reviewed-by: Martijn Coenen <maco@android.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
CC: stable@vger.kernel.org # Prerequisite for "writeback: Avoid skipping inode writeback"
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/fs-writeback.c