* Re: [PATCH] nsproxy: Check to make sure count is truly zero before freeing [not found] ` <20131118190457.7ad4e0a0@gandalf.local.home> @ 2013-11-19 1:22 ` Gao feng 2013-11-19 1:59 ` Steven Rostedt 0 siblings, 1 reply; 2+ messages in thread From: Gao feng @ 2013-11-19 1:22 UTC (permalink / raw) To: Steven Rostedt, Eric W. Biederman Cc: LKML, netdev@vger.kernel.org, David Miller, Cedric Le Goater, Paul E. McKenney, Pavel Emelyanov, Andrew Morton, Clark Williams, Arnaldo Carvalho de Melo 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. Thanks. ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] nsproxy: Check to make sure count is truly zero before freeing 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 0 siblings, 0 replies; 2+ messages in thread From: Steven Rostedt @ 2013-11-19 1:59 UTC (permalink / raw) To: Gao feng Cc: Eric W. Biederman, LKML, netdev@vger.kernel.org, David Miller, Cedric Le Goater, Paul E. McKenney, Pavel Emelyanov, Andrew Morton, Clark Williams, Arnaldo Carvalho de Melo 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-11-19 1:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 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).