linux-kernel - preempt-rt, need old style rwlocks for systemtap

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-next>] [day] [month] [year] [list]

Message-ID: <20080503132327.GA28881@redhat.com>
Date:	Sat, 3 May 2008 09:23:27 -0400
From:	"Frank Ch. Eigler" <fche@...hat.com>
To:	linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: preempt-rt, need old style rwlocks for systemtap

Hi -

It has come to my attention that the preempt-rt patch suite
deliberately defeats the potential concurrency intended by systemtap's
use of rwlocks to permit concurrent readers of various data
structures.  Since systemtap's probe handlers are all atomic,
nonblocking, nonpreemptable, it does not seem like there is any
real-time-oriented benefit in this.  What can we do to work around
this and permit reader concurrency again in preempt-rt?

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