From: Oleg Nesterov <oleg@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
rientjes@google.com, hannes@cmpxchg.org, linux-mm@kvack.org
Subject: Re: [REPOST] [PATCH 2/2] mm,oom: Reverse the order of setting TIF_MEMDIE and sending SIGKILL.
Date: Wed, 26 Aug 2015 16:28:52 +0200 [thread overview]
Message-ID: <20150826142851.GA30481@redhat.com> (raw)
In-Reply-To: <20150826141233.GI25196@dhcp22.suse.cz>
Hi Michal,
On 08/26, Michal Hocko wrote:
>
> I cannot seem to find any explicit note about task_lock vs. signal
> nesting nor task_lock() anywhere in kernel/signal.c so I rather ask. Can
> we call do_send_sig_info with task_lock held?
Yes.
Simply because task_lock() doesn't disable irqs and (unfortunately ;)
we do send the signals from interrupts.
Oleg.
--
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-26 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 7:19 [REPOST] [PATCH 2/2] mm,oom: Reverse the order of setting TIF_MEMDIE and sending SIGKILL Tetsuo Handa
2015-08-24 9:47 ` Michal Hocko
2015-08-25 12:06 ` Tetsuo Handa
2015-08-25 14:17 ` Michal Hocko
2015-08-25 14:37 ` Tetsuo Handa
2015-08-25 15:20 ` Michal Hocko
2015-08-26 14:12 ` Michal Hocko
2015-08-26 14:28 ` Oleg Nesterov [this message]
2015-08-27 8:38 ` Michal Hocko
2015-08-26 15:03 ` Tetsuo Handa
2015-08-27 8:40 ` Michal Hocko
2015-08-27 11:11 ` Tetsuo Handa
2015-08-27 11:34 ` Michal Hocko
2015-08-27 14:03 ` 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=20150826142851.GA30481@redhat.com \
--to=oleg@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.