linux-kernel - Re: [PATCH tip/core/rcu 0/9] Torture-test changes for 4.11

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 for Android: free password hash cracker in your pocket

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

Date:   Sat, 14 Jan 2017 21:39:46 -0800
From:   "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:     Josh Triplett <josh@...htriplett.org>
Cc:     linux-kernel@...r.kernel.org, mingo@...nel.org,
        jiangshanlai@...il.com, dipankar@...ibm.com,
        akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
        tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org,
        dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com,
        fweisbec@...il.com, oleg@...hat.com, bobby.prani@...il.com
Subject: Re: [PATCH tip/core/rcu 0/9] Torture-test changes for 4.11

On Sat, Jan 14, 2017 at 01:13:36PM -0800, Josh Triplett wrote:
> On Sat, Jan 14, 2017 at 01:25:33AM -0800, Paul E. McKenney wrote:
> > Hello!
> > 
> > This series provides torture-test updates:
> > 
> > 1.	Add a check for CONFIG_RCU_STALL_COMMON for TINY01, in order
> > 	to complain if this case is not tested.
> > 
> > 2.	Add CONFIG_PROVE_RCU_REPEATEDLY=y for TINY02, in order to test
> > 	this case.
> > 
> > 3.	Add tests without slow grace period setup/cleanup, as this case
> > 	is what is actually used in production.
> > 
> > 4.	Run at least one test with CONFIG_DEBUG_OBJECTS_RCU_HEAD, to make
> > 	sure that this case is tested regularly.
> > 
> > 5.	Run one test with DEBUG_LOCK_ALLOC but not PROVE_LOCKING, to make
> > 	sure that this case is tested regularly.
> > 
> > 6.	Run a couple scenarios with CONFIG_RCU_EQS_DEBUG, again to make
> > 	sure that this case is tested regularly.
> > 
> > 7.	Update RCU test scenario documentation.
> > 
> > 8.	Fix potential memory leak with rw lock test, courtesy of Yang Shi.
> > 
> > 9.	Enable DEBUG_OBJECTS_RCU_HEAD for Tiny RCU, you guessed it, to
> > 	make sure that this case is regularly tested.
> 
> Reviewed-by: Josh Triplett <josh@...htriplett.org>

Applied, thank you!

							Thanx, Paul