From: Michal Hocko <mhocko@kernel.org>
To: Liu Bo <bo.liu@linux.alibaba.com>
Cc: Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RFC] Ext4: fix deadlock on dirty pages between fault and writeback
Date: Mon, 10 Dec 2018 18:59:56 +0100 [thread overview]
Message-ID: <20181210175956.GW1286@dhcp22.suse.cz> (raw)
In-Reply-To: <20181207185102.2chvdfqwav5z6b7j@US-160370MP2.local>
On Fri 07-12-18 10:51:04, Liu Bo wrote:
> On Fri, Dec 07, 2018 at 12:20:36PM +0100, Michal Hocko wrote:
> > On Fri 07-12-18 08:16:15, Michal Hocko wrote:
> > [...]
> > > Memcg v1 indeed doesn't have any dirty IO throttling and this is a
> > > poor's man workaround. We still do not have that AFAIK and I do not know
> > > of an elegant way around that. Fortunatelly we shouldn't have that many
> > > GFP_KERNEL | __GFP_ACCOUNT allocations under page lock and we can work
> > > around this specific one quite easily. I haven't tested this yet but the
> > > following should work
> > >
> > > diff --git a/mm/memory.c b/mm/memory.c
> > > index 4ad2d293ddc2..59c98eeb0260 100644
> > > --- a/mm/memory.c
> > > +++ b/mm/memory.c
> > > @@ -2993,6 +2993,16 @@ static vm_fault_t __do_fault(struct vm_fault *vmf)
> > > struct vm_area_struct *vma = vmf->vma;
> > > vm_fault_t ret;
> > >
> > > + /*
> > > + * Preallocate pte before we take page_lock because this might lead to
> > > + * deadlocks for memcg reclaim which waits for pages under writeback.
> > > + */
> > > + if (!vmf->prealloc_pte) {
> > > + vmf->prealloc_pte = pte_alloc_one(vmf->vma->vm>mm, vmf->address);
> > > + if (!vmf->prealloc_pte)
> > > + return VM_FAULT_OOM;
> > > + }
> > > +
> > > ret = vma->vm_ops->fault(vmf);
> > > if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE | VM_FAULT_RETRY |
> > > VM_FAULT_DONE_COW)))
> >
> > This is too eager to allocate pte even when it is not really needed.
> > Jack has also pointed out that I am missing a write barrier. So here we
> > go with an updated patch. This is essentially what fault around code
> > does.
> >
>
> Makes sense to me, unfortunately we don't have a local reproducer to verify it
> and we've disabled CONFIG_MEMCG_KMEM to workaround the problem. Given the stack
> I put, the patch should address the deadlock at least.
OK, I will send a full patch with the changelog tomorrow.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2018-12-10 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1540858969-75803-1-git-send-email-bo.liu@linux.alibaba.com>
[not found] ` <20181127114249.GH16301@quack2.suse.cz>
[not found] ` <20181128201122.r4sec265cnlxgj2x@US-160370MP2.local>
[not found] ` <20181129085238.GD31087@quack2.suse.cz>
[not found] ` <20181129120253.GR6311@dastard>
[not found] ` <20181129130002.GM31087@quack2.suse.cz>
[not found] ` <20181129204019.GS6311@dastard>
2018-12-05 17:06 ` Jan Kara
2018-12-07 5:20 ` Dave Chinner
2018-12-07 7:16 ` Michal Hocko
2018-12-07 11:20 ` Michal Hocko
2018-12-07 18:51 ` Liu Bo
2018-12-10 17:59 ` Michal Hocko [this message]
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=20181210175956.GW1286@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=bo.liu@linux.alibaba.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@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