From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: rientjes@google.com, hannes@cmpxchg.org, linux-mm@kvack.org
Subject: Re: [REPOST] [PATCH 1/2] mm: Fix race between setting TIF_MEMDIE and __alloc_pages_high_priority().
Date: Mon, 24 Aug 2015 15:20:07 +0200 [thread overview]
Message-ID: <20150824132006.GN17078@dhcp22.suse.cz> (raw)
In-Reply-To: <201508242152.HHB69241.OFJLFVtFHQOMSO@I-love.SAKURA.ne.jp>
On Mon 24-08-15 21:52:08, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > The comment above the check is misleading but now you are allowing to
> > fail all ALLOC_NO_WATERMARKS (without __GFP_NOFAIL) allocations before
> > entering the direct reclaim and compaction. This seems incorrect. What
> > about __GFP_MEMALLOC requests?
>
> So, you want __GPP_MEMALLOC to retry forever unless TIF_MEMDIE is set, don't
> you?
I am not saying that. I was just pointing out that you have changed the
behavior of this gfp flag.
> > I think the check for TIF_MEMDIE makes more sense here.
>
> Since we already failed to allocate from memory reserves, I don't know if
> direct reclaim and compaction can work as expected under such situation.
Yes the allocation has failed and the reclaim might not do any
progress. Withtout trying to the reclaim we simply do not know that,
though.
The TIF_MEMDIE check was explicit for a good reason IMO. The race is not
really that important AFAICS because we would only fail the allocation
sooner for the OOM victim and that one might fail already. I might be
missing something of course but your change has a higher risk of
undesired behavior than the original code.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-08-24 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 7:21 Tetsuo Handa
2015-08-24 10:03 ` Michal Hocko
2015-08-24 12:52 ` Tetsuo Handa
2015-08-24 13:20 ` Michal Hocko [this message]
2015-08-27 13:49 ` Tetsuo Handa
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=20150824132006.GN17078@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rientjes@google.com \
/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