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] [day] [month] [year] [list]
Date:	Tue, 30 Sep 2014 00:57:00 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Davidlohr Bueso <dave@...olabs.net>
Cc:	peterz@...radead.org, mingo@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] locktorture: Torture rwlocks

On Mon, Sep 29, 2014 at 06:14:22AM -0700, Davidlohr Bueso wrote:
> We are still missing the ability to torture rwlocks, particularly the
> new queued variant (patch 1). The rest of the patches are miscellaneous
> updates.
> 
> Hopefully the set is straightforward enough that it can still be
> considered for v3.18.

Queued, thank you!

Running a quick set of tests, if these pass, will send a pull request along.

							Thanx, Paul

> Davidlohr Bueso (4):
>   locktorture: Support rwlocks
>   locktorture: Fix __acquire annotation for spinlock irq
>   locktorture: Cannot hold read and write lock
>   locktorture: Cleanup header usage
> 
>  Documentation/locking/locktorture.txt              |   5 +
>  kernel/locking/locktorture.c                       | 141 ++++++++++++++++++---
>  .../selftests/rcutorture/configs/lock/CFLIST       |   1 +
>  .../selftests/rcutorture/configs/lock/LOCK04       |   6 +
>  .../selftests/rcutorture/configs/lock/LOCK04.boot  |   1 +
>  5 files changed, 137 insertions(+), 17 deletions(-)
>  create mode 100644 tools/testing/selftests/rcutorture/configs/lock/LOCK04
>  create mode 100644 tools/testing/selftests/rcutorture/configs/lock/LOCK04.boot
> 
> -- 
> 1.8.4.5
> 

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ