linux-kernel - Re: Threaded irqs + 100% CPU RT task = RCU stall

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 6 Mar 2013 16:58:54 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Threaded irqs + 100% CPU RT task = RCU stall

On Wed, 6 Mar 2013, Paul Gortmaker wrote:
> So, I guess the question is, whether we want to try and make the system
> fail in a more meaningful way -- kind of like the rt throttling message
> does - as it lets users know they've hit the wall?  Something watching

That Joe Doe should have noticed the throttler message, which came
before the stall, shouldn't he?

> for kstat_incr_softirqs traffic perhaps?  Or other options?

The rcu stall detector could use the softirq counter and if it did not
change in the stall period print: "Caused by softirq starvation" or
something like that.

Thanks,

	tglx


--
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/