mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-api@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fork: report pid reservation failure properly
Date: Fri, 27 Feb 2015 09:22:16 +0100	[thread overview]
Message-ID: <20150227082216.GB30001@dhcp22.suse.cz> (raw)
In-Reply-To: <20150226144908.5e3d354d7b24174e90089721@linux-foundation.org>

On Thu 26-02-15 14:49:08, Andrew Morton wrote:
> On Mon, 23 Feb 2015 21:17:01 +0100 Michal Hocko <mhocko@suse.cz> wrote:
> 
> > ping on this one? Should I just resend (your way Andrew)? Or are there
> > any objections to the patch as is.
> 
> Were Eric's concerns all addressed?

I hope so. I didn't touch pid namespace parts and they return ENOMEM as
before.

> Oleg: wake up ;)
> 
> Overall it looks like a pretty minor issue?

I believe so. It should help deubugging when pid space is exhausted
because getting ENOMEM under that situation is really awkward and the
real reason for failure is hard to find out.

-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2015-02-27  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 15:05 [RFC PATCH] " Michal Hocko
2015-02-03 15:33 ` Michael Kerrisk (man-pages)
2015-02-03 15:52   ` Michal Hocko
2015-02-03 20:44     ` Eric W. Biederman
2015-02-04 10:27       ` Michal Hocko
2015-02-04 10:43         ` [PATCH] " Michal Hocko
2015-02-23 20:17           ` Michal Hocko
2015-02-26 22:49             ` Andrew Morton
2015-02-27  8:22               ` 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=20150227082216.GB30001@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=oleg@redhat.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®