linux-kernel - Re: [PATCH -tip-rcu] Make rcutorture more vicious: invoke RCU readers from irq handlers (timers)

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]

Message-ID: <20080626072239.GB3160@elte.hu>
Date:	Thu, 26 Jun 2008 09:22:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, josh@...edesktop.org,
	dvhltc@...ibm.com, niv@...ibm.com, dino@...ibm.com,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	vegard.nossum@...il.com, adobriyan@...il.com, oleg@...sign.ru,
	bunk@...nel.org, rjw@...k.pl
Subject: Re: [PATCH -tip-rcu] Make rcutorture more vicious: invoke RCU
	readers from irq handlers (timers)


* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:

> This patch allows torturing RCU from irq handlers (timers, in this 
> case). A new module parameter irqreader enables such additional 
> torturing, and is enabled by default.  Variants of RCU that do not 
> tolerate readers being called from irq handlers (e.g., SRCU) ignore 
> irqreader.
> 
> (No failures observed, but only short tests thus far.  And no failures 
> observed thus far from about 10 hours of running stock rcutorture in 
> parallel with 170 kernel builds on a two-CPU machine.)

applied to tip/core/rcu - thanks Paul.

> +static int irqreader = 1;	/* RCU readers from irq (timers). */

Good - this means that in bzImage type of tests (built-in rcutorture, no 
modules) this new test variant will be activated by default, right?

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