linux-kernel - Re: LTTng "TIF_KERNEL

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:	Tue, 28 Apr 2009 12:52:30 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
cc:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Ingo Molnar <mingo@...e.hu>, Li Zefan <lizf@...fujitsu.com>,
	linux-kernel@...r.kernel.org
Subject: Re: LTTng "TIF_KERNEL_TRACE"


On Tue, 28 Apr 2009, Frederic Weisbecker wrote:

> On Tue, Apr 28, 2009 at 12:38:25PM -0400, Mathieu Desnoyers wrote:
> > No, read-write lock is a "special case" where it does not deadlock if
> > you have an interrupt handler taking the read lock over another read
> > lock. It's just the write lock that _must absolutely_ disable
> > interrupts.
> 
> 
> Ah, you're right, I was thinking with spinlock rules in mind :)
> 

The only time you would want to do a read_lock_irqsave is if the 
write_lock is taken in irq context. But I do not know of any lock where 
that is the case.

-- Steve

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