linux-kernel - Re: rtmutex's wait

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: <1161683163.22373.68.camel@localhost.localdomain>
Date:	Tue, 24 Oct 2006 11:46:03 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Esben Nielsen <nielsen.esben@...glemail.com>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: rtmutex's wait_lock in 2.6.18-rt7

On Mon, 2006-10-23 at 11:55 +0200, Esben Nielsen wrote:
> Hi,
>   I see that in 2.6.18-rt7 the rtmutex's wait_lock is sudden interrupt 
> disabling. I don't see the need as no (hard) interrupt-handlers should be 
> touching any mutex.

It does not touch mutexes, but the dynamic priority adjustment of the
hrtimer softirq needs it. 

The correct solution will be moving the timer callback into the process
context, as it will be woken up anyway, but that's more complex to do
than it looks in the first place.

	tglx


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