writeback: don't warn on an unregistered BDI in __mark_inode_dirty

BDIs get unregistered during device removal, and this WARN can be
trivially triggered by hot-removing a NVMe device while running fsx
It is otherwise harmless as we still hold a BDI reference, and the
writeback has been shut down already.

Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Christoph Hellwig <[email protected]>
Signed-off-by: Jan Kara <[email protected]>

diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index e6005c78bfa93e0e1d2954dc68c576faec7a7699..acfb55834af23c437d4e166b50d15486c200a709 100644 (file)
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -2321,10 +2321,6 @@ void __mark_inode_dirty(struct inode *inode, int flags)
 
                        wb = locked_inode_to_wb_and_lock_list(inode);
 
-                       WARN((wb->bdi->capabilities & BDI_CAP_WRITEBACK) &&
-                            !test_bit(WB_registered, &wb->state),
-                            "bdi-%s not registered\n", bdi_dev_name(wb->bdi));
-
                        inode->dirtied_when = jiffies;
                        if (dirtytime)
                                inode->dirtied_time_when = jiffies;