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:21:21 +0000 (11:21 +0200)
commit92f10de407caffdcf30c67ec3c482e3892cdf9fb
treef5c049b6c25da4e8bf0c99bd57eb0139dca10187
parent673d5fb7ac8a7c6cfa579f788e07b3a8bcc50d23
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