linux-kernel - Re: sys_sched_yield keeps locked irq before call of schedule()

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]

Date:	Wed, 5 Nov 2008 15:05:15 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	"Zdenek Kabelac" <zdenek.kabelac@...il.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>
Subject: Re: sys_sched_yield keeps locked irq before call of schedule()

On Wednesday 05 November 2008, Zdenek Kabelac wrote:
> > is this some special warning you added? The stock kernel certainly
> > does not emit this warning.
> 
> Yes - it's my personal debug checker that tries to watch wether irq &
> irqsafe are running in pair.
> So it shows a warning if there is a call of spin_lock_irq and irq is
> already dissabled.

I've done such a checker before as well, but back then it showed
far too many false positives. If you have a working version, can you
post your patch here? I think that would be very useful in the kernel.

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