From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Wagin <avagin@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Pavel Emelyanov <xemul@openvz.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: general protection fault on finalizing task
Date: Fri, 15 Jun 2012 11:42:03 +0200 [thread overview]
Message-ID: <20120615094202.GA16768@redhat.com> (raw)
In-Reply-To: <CANaxB-z3Jho4vjRcG30mECYO+CdjwHXX7TmvxCy2A8rp2J7AOA@mail.gmail.com>
Hi Andrew,
Thanks lot for testing, I guess we need these fixes in 3.5
But I am puzzled...
On 06/15, Andrew Wagin wrote:
>
> FYI: I bisected this problem.
>
> # git bisect bad
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [3208450488ae724196f1efffc457e4265957c04e] pidns: use
> task_active_pid_ns in do_notify_parent
>
> commit 3208450488ae724196f1efffc457e4265957c04e
> Author: Eric W. Biederman <ebiederm@xmission.com>
> Date: Thu May 31 16:26:39 2012 -0700
>
> pidns: use task_active_pid_ns in do_notify_parent
Impossible ;) I think. I'd say it should be the next change
00c10bc13cdb58447d6bb2a003afad7bd60f5a5f
"pidns: make killed children autoreap"
which is fine by itself, but makes the problem (hopefully fixed
by -mm patches) more visible.
Oleg.
next prev parent reply other threads:[~2012-06-15 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 8:03 general protection fault on finalizing task Andrey Vagin
2012-06-14 16:01 ` Oleg Nesterov
2012-06-14 20:37 ` Andrew Wagin
2012-06-15 9:42 ` Oleg Nesterov [this message]
2012-06-14 21:05 ` Andrew Wagin
2012-06-14 22:28 ` Andrew Morton
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=20120615094202.GA16768@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xemul@openvz.org \
/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