linux-kernel - Re: [PATCH] [KGDB] core code cleanups

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080127065734.GA29514@elte.hu>
Date:	Sun, 27 Jan 2008 07:57:34 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	jason.wessel@...driver.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, hpa@...or.com
Subject: Re: [PATCH] [KGDB] core code cleanups

* Andrew Morton <akpm@...ux-foundation.org> wrote:

> > thanks Jason, i have applied your cleanups to x86.git.
> 
> I don't recall having actually seen the kgdb patches recently.  Have 
> they had a suitable level of review?

it was posted three months ago to lkml (the upteenth time) and we picked 
it up into x86.git a month ago. KGDB has been problem-free in x86.git 
ever since.

> In particular, as the plan is to migrate all kgdb-enabled 
> architectures onto the generic kgdb core (yes?), have the owners of 
> the eligible architectures actually taken a look at what we'll be 
> asking of them?

at least as far as x86.git went the arch impact was refreshingly small. 
There was some feedback that was addressed by Jason. (If any feedback is 
still unaddressed then let us know - or if there are any new comments 
i'm sure they will be addressed prompty - please keep the comments 
coming!)

As more architectures enable support for KGDB, any specific objections 
can and should be addressed on that level. (That's how we did it for 
genirq and dynticks and that went far better than "address all 
architecture concerns at once" - which delays merges forever. We'd still 
be discussing irq flows versus flat irqs and clockevents versus drivers 
if we did it like that.)

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