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]

Message-ID: <Pine.LNX.4.64.0610021529260.3952@g5.osdl.org>
Date:	Mon, 2 Oct 2006 15:33:38 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Andi Kleen <ak@...e.de>
cc:	Andrew Morton <akpm@...l.org>, Ingo Molnar <mingo@...e.hu>,
	David Howells <dhowells@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	Dmitry Torokhov <dtor@...l.ru>, Greg KH <greg@...ah.com>,
	David Brownell <david-b@...bell.net>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than
 passing to IRQ handlers

On Mon, 2 Oct 2006, Andi Kleen wrote:
> 
> I remember trying to compile a lot of architectures when I did 4level,
> but I quickly gave up because of many of them just didn't without
> me changing anything.

I think that if we cover x86-64 and plain old x86 with something like 
"allmodconfig", and just doing a best effort on the other architectures, 
we're already in pretty damn good shape. It's not like fixing any stupid 
left-overs that got missed because some "grep" pattern didn't notice an 
odd user is going to really cause problems.

I don't think the architecture maintainers will have any trouble 
converting their own architecture. It's literally a question of getting 
clear compiler warnings or errors, and just fixing them up. I'll do at 
least the parts of ppc64 that I'd notice myself, unless somebody else just 
gets to it first.

So I really wouldn't worry about any small short-term problems. The reason 
I mentioned out-of-tree drivers is exactly the fact that they can't just 
fix it up trivially for a single flag-day, so they have to have a longer- 
term solution.

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