From: David Rientjes <rientjes@google.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org, Michal Hocko <mhocko@suse.cz>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Patch] freezer: check OOM kill signal while being frozen
Date: Sat, 9 Aug 2014 01:55:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1408090152240.11855@chino.kir.corp.google.com> (raw)
In-Reply-To: <1407545198-9009-1-git-send-email-xiyou.wangcong@gmail.com>
On Fri, 8 Aug 2014, Cong Wang wrote:
> diff --git a/kernel/freezer.c b/kernel/freezer.c
> index aa6a8aa..c6d189d 100644
> --- a/kernel/freezer.c
> +++ b/kernel/freezer.c
> @@ -68,7 +68,9 @@ bool __refrigerator(bool check_kthr_stop)
> spin_lock_irq(&freezer_lock);
> current->flags |= PF_FROZEN;
> if (!freezing(current) ||
> - (check_kthr_stop && kthread_should_stop()))
> + (check_kthr_stop && kthread_should_stop()) ||
> + (test_tsk_thread_flag(current, TIF_MEMDIE) &&
> + fatal_signal_pending(current)))
> current->flags &= ~PF_FROZEN;
> spin_unlock_irq(&freezer_lock);
>
All threads with TIF_MEMDIE set would have been killed, why is the check
for fatal_signal_pending(current) needed?
You can also use test_thread_flag(TIF_MEMDIE) instead since you're only
concerned with current.
Furthermore, that conditional is getting difficult to read. Maybe it
would help to have a helper function that returns bool that determines
whether PF_FROZEN should be cleared?
next prev parent reply other threads:[~2014-08-09 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 0:46 Cong Wang
2014-08-09 2:00 ` Kyungmin Park
2014-08-09 3:05 ` Cong Wang
2014-08-09 8:55 ` David Rientjes [this message]
2014-08-12 0:20 ` Cong Wang
2014-08-11 13:18 ` Michal Hocko
2014-08-12 0:34 ` Cong Wang
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=alpine.DEB.2.02.1408090152240.11855@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=rjw@rjwysocki.net \
--cc=tj@kernel.org \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®