From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] writeback: don't warn on an unregistered BDI in __mark_inode_dirty
Date: Wed, 9 Dec 2020 17:35:36 +0100 [thread overview]
Message-ID: <20201209163536.GA2587@quack2.suse.cz> (raw)
In-Reply-To: <20200928122613.434820-1-hch@lst.de>
On Mon 28-09-20 14:26:13, Christoph Hellwig wrote:
> 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.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>
> I have a vague memory someone else sent this patch alredy, but couldn't
> find it in my mailing list folder. But given that my current NVMe
> tests trigger it easily I'd rather get it fixed ASAP.
Did this patch get lost? I don't see it upstream or in Jens' tree. FWIW I
agree the warning may result in false positive so I'm OK with removing it.
So feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
>
> fs/fs-writeback.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index e6005c78bfa93e..acfb55834af23c 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;
> --
> 2.28.0
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-12-09 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 12:26 [PATCH] writeback: don't warn on an unregistered BDI in __mark_inode_dirty Christoph Hellwig
2020-12-09 16:35 ` Jan Kara [this message]
2020-12-09 17:47 ` Christoph Hellwig
2020-12-16 10:57 ` Jan Kara
2020-12-16 14:19 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201209163536.GA2587@quack2.suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).