linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
	David Rientjes <rientjes@google.com>,
	Sergey Dyasly <dserrg@gmail.com>, Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH] kthread: Make kthread_create() killable.
Date: Sun, 15 Sep 2013 18:55:31 +0200	[thread overview]
Message-ID: <20130915165531.GD13344@redhat.com> (raw)
In-Reply-To: <201309152038.DDJ59271.OJMOHLFtSFOQVF@I-love.SAKURA.ne.jp>

Hi Tetsuo,

please do not start the off-list discussions ;)

On 09/15, Tetsuo Handa wrote:
>
> I examined do_coredump() case and found similar result.

...

> Do we want to change from call_usermodehelper_exec(UMH_WAIT_EXEC) to
> call_usermodehelper_exec(UMH_WAIT_EXEC | UMH_WAIT_KILLABLE)

To me, this makes sense in any case. And this matches other recent
"make coredump killable" changes.

> thread (who is waiting for pipe reader process to start) can terminate as soon
> as possible (rather than waiting forever unless somebody releases memory)?

But as for OOM this can't help if the dumping process is multithreaded.
This connects to other problems we discuss in another thread. probably
I should send the patch which does s/PT_TRACE_EXIT/SIGNAL_GROUP_COREDUMP/
at least.

Oleg.


  parent reply	other threads:[~2013-09-15 17:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201309132318.HEC05218.OtVOFOFMLJHFQS@I-love.SAKURA.ne.jp>
2013-09-14 16:05 ` [PATCH] kthread: Make kthread_create() killable Oleg Nesterov
2013-09-14 23:46   ` Tetsuo Handa
2013-09-15 16:39     ` Oleg Nesterov
2013-09-16  0:53       ` [PATCH v2] " Tetsuo Handa
2013-09-23 23:07         ` Andrew Morton
2013-09-24 15:17           ` [PATCH v3] " Tetsuo Handa
2013-09-24 16:38             ` Oleg Nesterov
2013-09-25 21:05             ` David Rientjes
2013-09-26  2:59               ` Tetsuo Handa
2013-09-26 18:53                 ` David Rientjes
2013-09-28  7:18                   ` Tetsuo Handa
2013-09-30 21:57                     ` David Rientjes
2013-10-01 13:20                       ` Tetsuo Handa
2013-10-02  7:06                         ` David Rientjes
2013-10-02 13:44                           ` Tetsuo Handa
     [not found]     ` <201309152038.DDJ59271.OJMOHLFtSFOQVF@I-love.SAKURA.ne.jp>
2013-09-15 16:55       ` Oleg Nesterov [this message]
2013-09-16  7:25         ` [PATCH] coredump: Make startup of coredump to pipe killable 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=20130915165531.GD13344@redhat.com \
    --to=oleg@redhat.com \
    --cc=dserrg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rientjes@google.com \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).