From: Steven Rostedt <rostedt@goodmis.org>
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
LKML <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Cedric Le Goater <clg@fr.ibm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Pavel Emelyanov <xemul@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
Clark Williams <williams@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] nsproxy: Check to make sure count is truly zero before freeing
Date: Mon, 18 Nov 2013 20:59:09 -0500 [thread overview]
Message-ID: <20131118205909.6bc27f0e@gandalf.local.home> (raw)
In-Reply-To: <528ABD6E.8020004@cn.fujitsu.com>
On Tue, 19 Nov 2013 09:22:54 +0800
Gao feng <gaofeng@cn.fujitsu.com> wrote:
> On 11/19/2013 08:04 AM, Steven Rostedt wrote:
> >
> > I'll start out saying that this email was a complete oops. I only kept
> > it around for reference, as this didn't fix the bug we were seeing, and
> > I used this email to just document what I initially thought.
> >
>
> Can you describe the panic situation and the way to reproduce?
> it's useful for us to find out the real problem.
>
I need to talk with more people to get more information as it happened
in our test labs. From what I remember, it was caused on 3.10-rt (even
with PREEMPT_RT disabled). We are currently testing 3.10 vanilla, to
make sure that it really does occur on mainline.
>From what I understand, it was ltp-lite that caused the panic and it
happened on a box with 16 CPUs.
I'll keep you posted when we get more data that is relevant to mainline.
This is another reason that the email went out prematurely.
-- Steve
prev parent reply other threads:[~2013-11-19 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131113160339.7e0726fb@gandalf.local.home>
[not found] ` <877gc5l3hq.fsf@xmission.com>
[not found] ` <20131118190457.7ad4e0a0@gandalf.local.home>
2013-11-19 1:22 ` [PATCH] nsproxy: Check to make sure count is truly zero before freeing Gao feng
2013-11-19 1:59 ` Steven Rostedt [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=20131118205909.6bc27f0e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=clg@fr.ibm.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=gaofeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=williams@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).