From: Coly Li <colyli@suse.de>
To: Eddie Chapman <eddie@ehuk.net>
Cc: guoju <fangguoju@gmail.com>,
kent.overstreet@gmail.com, linux-bcache@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcache: add separate workqueue for journal_write to avoid deadlock
Date: Fri, 28 Sep 2018 10:32:53 +0800 [thread overview]
Message-ID: <ef36fbef-9f2e-0208-aa00-bd9ba656de31@suse.de> (raw)
In-Reply-To: <9b1abe65-c6f5-77b4-290e-e6af21723cfc@ehuk.net>
On 9/27/18 11:53 PM, Eddie Chapman wrote:
> On 27/09/18 16:23, Coly Li wrote:
>>
>> On 9/27/18 9:45 PM, guoju wrote:
>>> After write SSD completed, bcache schedule journal_write work to
>>> system_wq, that is a public workqueue in system, without WQ_MEM_RECLAIM
>>> flag. system_wq is also a bound wq, and there may be no idle kworker on
>>> current processor. Creating a new kworker may unfortunately need to
>>> reclaim memory first, by shrinking cache and slab used by vfs, which
>>> depends on bcache device. That's a deadlock.
>>>
>>> This patch create a new workqueue for journal_write with WQ_MEM_RECLAIM
>>> flag. It's rescuer thread will work to avoid the deadlock.
>>>
>>> Signed-off-by: guoju <fangguoju@gmail.com>
>>
>> Nice catch, this fix is quite important. I will try to submit to Jens
>> ASAP.
>>
>> Thanks.
>>
>> Coly Li
>
> Once this goes into 4.19, would this be a candidate for backporting to
> any stable kernels, or does it only fix something introduced in this
> cycle?
>
This bug exists in upstream for quite long time, it should be applied to
all stable kernels which it can be applied. And it is Cced to
stable@vger.kernel.org already.
Coly Li
next prev parent reply other threads:[~2018-09-28 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 13:45 [PATCH] bcache: add separate workqueue for journal_write to avoid deadlock guoju
2018-09-27 15:23 ` Coly Li
2018-09-27 15:53 ` Eddie Chapman
2018-09-27 20:18 ` Stefan Priebe - Profihost AG
[not found] ` <2C0DE6F7-624B-49B6-9788-BA0A8E7DA25C@profihost.ag>
2018-09-28 2:31 ` Coly Li
2018-09-28 2:32 ` Coly Li [this message]
2018-10-04 14:07 ` Eddie Chapman
2018-10-16 6:27 ` Coly Li
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=ef36fbef-9f2e-0208-aa00-bd9ba656de31@suse.de \
--to=colyli@suse.de \
--cc=eddie@ehuk.net \
--cc=fangguoju@gmail.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@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