| 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: <20110531125902.GA13217@Chamillionaire.breakpoint.cc> Date: Tue, 31 May 2011 14:59:02 +0200 From: Sebastian Andrzej Siewior <sebastian@...akpoint.cc> To: Thomas Gleixner <tglx@...utronix.de> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 3/3] irq: catch more wrong return values from interrupt handlers * Thomas Gleixner | 2011-05-31 12:32:58 [+0200]: >On Tue, 31 May 2011, Sebastian Andrzej Siewior wrote: > >> We now also accept return value IRQ_WAKE_THREAD from a threaded >> interrupt or IRQ_HANDLED | IRQ_WAKE_THREAD from primary and theaded >> handler which is wrong. We need to accept the later on shared handlers >> where one handler is primary only and the second is a threaded handler. >> This patch attempts to catch them. Unfortunately this patch introduces >> two new types so I'm not sure if it is worth it. > >I'd rather avoid that ugliness. If driver writers are that stupid, >there is probably more significant wreckage than this. Sure. It is just that the "old" code ensured that either NONE or HANDLED is returned and nothing else and the previous patch broke that check. This patch just points it out :) Do you want bad_action_ret() removed or kept as it? >Thanks, > > tglx Sebastian -- 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