From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: mhocko@suse.cz, hannes@cmpxchg.org, rientjes@google.com,
linux-mm@kvack.org, Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: What is oom_killer_disable() for?
Date: Tue, 12 Jan 2016 13:38:09 +0100 [thread overview]
Message-ID: <2751070.RBiEJZRJTx@vostro.rjw.lan> (raw)
In-Reply-To: <201601121917.IEI30296.OVOFFtQSLFHJOM@I-love.SAKURA.ne.jp>
On Tuesday, January 12, 2016 07:17:19 PM Tetsuo Handa wrote:
> Michal Hocko write:
[cut]
> > I am not sure I am following you here but how do you detect that the
> > userspace has corrupted your image or accesses an already (half)
> > suspended device or something similar?
>
> Can't we determine whether the OOM killer might have corrupted our image
> by checking whether oom_killer_disabled is kept true until the point of
> final decision?
The freezing is really not about keeping the image consistent etc. It is
not about hibernation specifically even.
> To me, satisfying allocation requests by kernel threads by invoking the
> OOM killer and aborting suspend operation if the OOM killer was invoked
> sounds cleaner than forcing !__GFP_NOFAIL allocation requests to fail.
What if the suspend is on emergency, like low battery or thermal?
Thanks,
Rafael
--
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:[~2016-01-12 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 11:04 [PATCH] mm,oom: make oom_killer_disable() killable Tetsuo Handa
2016-01-09 17:02 ` What is oom_killer_disable() for? Tetsuo Handa
2016-01-11 14:49 ` Michal Hocko
2016-01-12 10:17 ` Tetsuo Handa
2016-01-12 12:38 ` Rafael J. Wysocki [this message]
2016-01-12 12:17 ` Rafael J. Wysocki
2016-01-11 14:12 ` [PATCH] mm,oom: make oom_killer_disable() killable Michal Hocko
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=2751070.RBiEJZRJTx@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=mhocko@suse.cz \
--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