From: ebiederm@xmission.com (Eric W. Biederman)
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Rakib Mullick <rakib.mullick@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [nsproxy] BUG: unable to handle kernel NULL pointer dereference at 0000000000000024
Date: Thu, 07 Mar 2013 09:23:35 -0800 [thread overview]
Message-ID: <87sj47t97s.fsf@xmission.com> (raw)
In-Reply-To: <20130307132819.GA31162@localhost> (Fengguang Wu's message of "Thu, 7 Mar 2013 21:28:19 +0800")
Fengguang Wu <fengguang.wu@intel.com> writes:
> Greetings,
>
> I got the below oops and the first bad commit is
Doh! On a second look that change is totally wrong. Of course we need
to up the ref-count every time we create a new process. Especially if
we don't do anything with namespaces.
I was looking at it from the wrong angle last night. I should have
known better.
Patch dropped.
Thanks,
Eric
next prev parent reply other threads:[~2013-03-07 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 13:28 [nsproxy] BUG: unable to handle kernel NULL pointer dereference at 0000000000000024 Fengguang Wu
2013-03-07 17:23 ` Eric W. Biederman [this message]
2013-03-08 11:38 ` Rakib Mullick
2013-03-08 16:01 ` Eric W. Biederman
2013-03-09 3:54 ` Rakib Mullick
2013-03-09 8:33 ` Eric W. Biederman
2013-03-09 16:48 ` Rakib Mullick
2013-03-11 8:12 ` Rakib Mullick
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=87sj47t97s.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rakib.mullick@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