lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 1 Dec 2015 11:55:37 -0800 From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> To: fupan li <lifupan@...il.com> Cc: linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: RCU stall and the system boot hang On Mon, Nov 30, 2015 at 09:19:18AM -0800, Paul E. McKenney wrote: > On Mon, Nov 30, 2015 at 02:54:13PM +0800, fupan li wrote: [ . . . ] > > No, just a normal boot, and these stalls were happened before > > systemd services running. > > Interesting. My testing show v4.1 being OK, with the first issues showing > up somewhere between v4.1 and v4.2. Or at least v4.1 is reliable enough > that is passes 42 hours of focused rcutorture testing, where v4.2 tends > to fail in under two hours. And it seems to happen only on multisocket > systems -- I seem to be able to hammer as hard as I want on my four-core > (eight hardware thread) laptop without an issue. And I take it back. After beating on it for the better part of a week, I did get one failure on my single-socket laptop. So maybe I need to make my rcutorture scripts force tests to cross socket boundaries where possible... Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists