| 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
| ||
|
Message-ID: <1348489027.11847.53.camel@twins> Date: Mon, 24 Sep 2012 14:17:07 +0200 From: Peter Zijlstra <a.p.zijlstra@...llo.nl> To: Daniel Vetter <daniel.vetter@...ll.ch> Cc: LKML <linux-kernel@...r.kernel.org>, Intel Graphics Development <intel-gfx@...ts.freedesktop.org>, DRI Development <dri-devel@...ts.freedesktop.org>, Dave Airlie <airlied@...il.com>, Thomas Gleixner <tglx@...utronix.de>, Alan Cox <alan@...rguk.ukuu.org.uk> Subject: Re: [PATCH 2/2] [RESEND] console: implement lockdep support for console_lock On Tue, 2012-09-18 at 01:03 +0200, Daniel Vetter wrote: > - In the printk code there's a special trylock, only used to kick off > the logbuffer printk'ing in console_unlock. But all that happens > while lockdep is disable (since printk does a few other evil > tricks). So no issue there, either. Not particularly evil, just plain broken. See this series: http://marc.info/?l=linux-kernel&m=132446644123326&w=2 In particular see patches 1-4. The problem with lockdep is that lockdep uses printk and printk's recursion stuff is utterly broken. Console drivers being on crack simply doesn't help :-) Note that I would never recommend drm/ksm to anybody who really cares about their console output. -- 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/
Powered by blists - more mailing lists