linux-kernel - Re: [PATCH 3/3] IRQ: Maintain regs pointer 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]

Date:	Mon, 2 Oct 2006 13:46:11 -0700
From:	David Brownell <david-b@...bell.net>
To:	Andrew Morton <akpm@...l.org>, David Howells <dhowells@...hat.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	torvalds@...l.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, Dmitry Torokhov <dtor@...l.ru>,
	Greg KH <greg@...ah.com>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers

The only downside I can think of for dropping pt_regs is that now it's harder
to just find the IRQ handler in a driver ... it's previously been all but
guaranteed that the _only_ use of that type is the IRQ logic.  The upsides
surely outweigh that.

> >  (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
> >      something different depending on whether it's been supplied with a regs
> >      pointer or not.

gaak!  where did that come from?  I'll be surprised if removing
that causes any problem at all.

- Dave

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