linux-kernel - Re: [PATCH 05/37] kdb: core for kgdb back end

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:	Tue, 29 Dec 2009 00:37:34 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Jason Wessel <jason.wessel@...driver.com>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	kgdb-bugreport@...ts.sourceforge.net,
	Peter Zijlstra <peterz@...radead.org>, mingo@...e.hu,
	mort@....com, linux-arch@...r.kernel.org
Subject: Re: [PATCH 05/37] kdb: core for kgdb back end

On Mon, Dec 28, 2009 at 04:36:03PM -0600, Jason Wessel wrote:
> Andi Kleen wrote:
> > Jason Wessel <jason.wessel@...driver.com> writes:
> > 
> > I remember going with kaos through all the code
> > outside kdb/ in his own patch and for nearly all hooks
> > outside we found some way to eliminate them. 
> > 
> > I think a lot of this is here too.
> 
> 
> If this has been solved before somewhere, please point me in that direction.  There are whole lot few changes in this series vs original kdb outside of the kdb core area.

I don't think we ever generated patches, just reviewed all the changes
outside kdb/* and eventually agreed that it wasn't needed or could be done in a much
cleaner way.

Frankly some things can be also just dropped. Or if you're really desperate
about nops just nop the spinlock functions while kdb runs.

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