[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <071c4f38-df7b-b094-1bd0-436fcdb05767@windriver.com>
Date: Sun, 8 Mar 2020 19:00:22 +0800
From: He Zhe <zhe.he@...driver.com>
To: Christoph Hellwig <hch@....de>, Jan Kara <jack@...e.cz>
Cc: Jens Axboe <axboe@...nel.dk>, viro@...iv.linux.org.uk,
bvanassche@....org, keith.busch@...el.com, tglx@...utronix.de,
mwilck@...e.com, yuyufen@...wei.com, linux-block@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: disk revalidation updates and OOM
On 3/7/20 10:29 PM, Christoph Hellwig wrote:
> So I looked into this, and if it was just the uevent this
> should have been fixed in:
>
> "block: don't send uevent for empty disk when not invalidating"
>
> from Eric Biggers in December. Does the problem still occur with that
> patch applied?
Yes, it occurs with that patch. The patch that introduces the issue and the one
you mentioned above both went in in v5.5-rc1. I found this issue in v5.5
release.
Thanks,
Zhe
Powered by blists - more mailing lists