diff options
| author | Christoph Hellwig <hch@lst.de> | 2020-09-28 14:26:13 +0200 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2020-12-16 11:56:02 +0100 |
| commit | f7387170339afb473a0d95b7732f904346f9795e (patch) | |
| tree | 505166eb10ed08ffe2698f2ca01e8b5d27f2a191 /fs/fs-writeback.c | |
| parent | e51d68e76d604c6d5d1eb13ae1d6da7f6c8c0dfc (diff) | |
| download | linux-f7387170339afb473a0d95b7732f904346f9795e.tar.gz linux-f7387170339afb473a0d95b7732f904346f9795e.tar.bz2 linux-f7387170339afb473a0d95b7732f904346f9795e.zip | |
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/20200928122613.434820-1-hch@lst.de
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/fs-writeback.c')
| -rw-r--r-- | fs/fs-writeback.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c index e6005c78bfa9..acfb55834af2 100644 --- 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; |