lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 15 Mar 2010 09:46:02 +0800
From:	Li Zefan <>
CC:	Lai Jiangshan <>,
	Frederic Weisbecker <>,
	Américo Wang <>,
	LKML <>, Ingo Molnar <>
Subject: Re: 2.6.33: ftrace triggers soft lockup

Steven Rostedt wrote:
> On Fri, 2010-03-12 at 21:07 -0500, Steven Rostedt wrote:
>> On Tue, 2010-03-09 at 11:38 +0800, Li Zefan wrote:
>>> The segfault is from userspace. This is a segfault I just got:
>>> ftrace_stack_ma[14989]: segfault at fe2e ip 00000000004474c0 sp 00007fffb97e38c0 error 4 in bash[400000+d1000]
>> Li and Lai,
>> Thanks a lot for reporting all this, and writing the ftrace_stress_test.
>> I've fixed all the bugs that it has reported (to my knowledge) and after
>> a little more testing I will soon be sending a patch series out.
> Li,
> I ran your test for 13 hours on three different machines. I did not hit
> any more errors. Although I see a lockdep warning (not a locking problem
> but the WARN_ON in fork.c is triggering). I'll look into that on Monday.

As I said in the offline mail, this warning is caused by global trace_clock,
and I sent a fix sometime ago:

> Please take the new patches that Ingo just pushed to Linus, if you find
> any more bugs, please let me know right away.

Thanks for the fixes!

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists