linux-kernel - [PATCH, RAW] IRQ: Maintain irq number globally rather than passing to IRQ handlers

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: <452673AC.1080602@garzik.org>
Date:	Fri, 06 Oct 2006 11:18:04 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Howells <dhowells@...hat.com>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
CC:	Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...l.org>,
	Thomas Gleixner <tglx@...utronix.de>, torvalds@...l.org,
	Dmitry Torokhov <dtor@...l.ru>, Greg KH <greg@...ah.com>,
	David Brownell <david-b@...bell.net>,
	Alan Stern <stern@...land.harvard.edu>
Subject: [PATCH, RAW] IRQ: Maintain irq number globally rather than passing
 to IRQ handlers

Here is the raw, un-split-up first pass of the irq argument removal 
patch (500K):	http://gtf.org/garzik/misc/patch.irq-remove

Notes:

* raw first pass, DO NOT APPLY.

* this was useful work:  it turned up several minor bugs

* Do we mark irq handlers FASTCALL?  If not, we probably can now.

* I also turned up a few obvious places that dhowells missed in his 
pt_regs patch, inevitably in non-x86 arches that probably were not built.

* I need to fix up ~10 or so drivers that called their interrupt 
handlers directly, then used a 'irq == 0' test to determine whether the 
interrupt handler was called internally, or by the system.

* not sure yet if I want to mark the parport "irq handler" functions as 
truly irqreturn_t

* Hopefully I will have this polished by the end of the day.

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