Messages in this thread |  | | Date | Mon, 18 Nov 2013 20:59:09 -0500 | From | Steven Rostedt <> | Subject | Re: [PATCH] nsproxy: Check to make sure count is truly zero before freeing |
| |
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
|  |