| 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
| ||
|
Date: Tue, 02 Nov 2010 13:54:54 -0700 (PDT) From: David Miller <davem@...emloft.net> To: airlied@...il.com Cc: yong.zhang0@...il.com, peterz@...radead.org, mingo@...hat.com, jbarnes@...tuousgeek.org, linux-kernel@...r.kernel.org Subject: Re: lockdep and oops_in_progress From: Dave Airlie <airlied@...il.com> Date: Wed, 3 Nov 2010 06:51:07 +1000 >> commit e0fdace10e75dac67d906213b780ff1b1a4cc360 >> Author: David Miller <davem@...emloft.net> >> Date: Fri Aug 1 01:11:22 2008 -0700 >> >> debug_locks: set oops_in_progress if we will log messages. >> >> Otherwise lock debugging messages on runqueue locks can deadlock the >> system due to the wakeups performed by printk(). >> >> Signed-off-by: David S. Miller <davem@...emloft.net> >> Signed-off-by: Ingo Molnar <mingo@...e.hu> >> >> Seems we can revert that commit now because of 'robustify printk'. I completely agree, this can definitely be reverted. Thanks! -- 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