linux-kernel - Re: [PATCH] sound_core.c: Remove BKL from soundcore

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: <20091011201759.435cd93c@lxorguk.ukuu.org.uk>
Date:	Sun, 11 Oct 2009 20:17:59 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Jonathan Corbet <corbet@....net>, John Kacur <jkacur@...hat.com>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Vincent^M^J Sanders <vince@...tec.co.uk>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] sound_core.c: Remove BKL from soundcore_open

> it's getting time though to bite the bullet and make it a real normal
> mutex. Lockdep will then flag a bunch of sh*t we'll need to fix, but
> without doing that we're never going to really make progress. 

It won't. Instead you get situations like one ioctl blocking another to
an unrelated device that just causes weird failures and performance
problems, or in some cases deadlocks.

Open routines block so it takes about 5 seconds of thought to realise
that using a mutex here is brain dead and doesn't work.

You push the BKL down. Next step from the call point is to replicate it
inside each of the drivers that path can call, then in those drivers push
the lock_kernel down and the internal locking up. Eventually they meet in
the middle.

If you try and do botch jobs with bogus mutex hacks it breaks, it breaks
in ways lockdep doesn't understand and it doesn't even *help* fix the
problem proper.

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