linux-kernel - pcmcia's use of IRQ

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-next>] [day] [month] [year] [list]

Message-Id: <4B94DCB7020000780003337B@vpn.id2.novell.com>
Date:	Mon, 08 Mar 2010 10:17:11 +0000
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	<linux@...inikbrodowski.net>,
	"Andrew Morton" <akpm@...ux-foundation.org>, <alan@...ux.intel.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: pcmcia's use of IRQ_NOAUTOEN

(re-sending to correct Alan's email address)

Commit 635416ef393e8cec5a89fc6c1de710ee9596a51e introduced
this, but I can't see how it can take effect - the argument passed to
request_irq() only affects action->flags (IRQF_*), whereas the flag
in question is a desc->status one (IRQ_*). Am I overlooking
something? If not, while currently this just should not work as expected,
it's latently more significant (as soon as the IRQF_* definitions make
use of the bit used by IRQ_NOAUTOEN).

Thanks, Jan

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