mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Tejun Heo <tj@kernel.org>, David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: oom && coredump
Date: Tue, 2 Dec 2014 09:59:49 +0100	[thread overview]
Message-ID: <20141202085949.GA27014@dhcp22.suse.cz> (raw)
In-Reply-To: <20141127174747.GA7684@redhat.com>

On Thu 27-11-14 18:47:47, Oleg Nesterov wrote:
> On 11/27, Michal Hocko wrote:
[...]
> > Why is the ptrace check wrong?
> 
> It was added in reply to exploit I sent. But:
> 
> - It doesn't (and can't) really work, it can only detect this particular
>   case and the same exploit still blocks oom-killer with the minimal
>   modifications.
> 
> - Once again, this has nothing to do with ptrace. That exploit used
>   ptrace only to control (freeze) the coredumping process, the coredumping
>   can "hang" because of other reasons.
> 
> - It is no longer needed after this patch, the coredumping process will
>   be killed.

OK, I guess I am seeing it now. Thanks for the clarification!

[...]
-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2014-12-02  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 17:19 + oom-pm-oom-killed-task-cannot-escape-pm-suspend.patch added to -mm tree Oleg Nesterov
2014-10-20 18:46 ` Michal Hocko
2014-10-20 19:06   ` Oleg Nesterov
2014-10-20 19:56     ` oom && coredump Oleg Nesterov
2014-11-27 12:29       ` Michal Hocko
2014-11-27 17:47         ` Oleg Nesterov
2014-12-02  8:59           ` Michal Hocko [this message]

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=20141202085949.GA27014@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=rientjes@google.com \
    --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®