linux-kernel - Re: [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb!

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: <20060830155710.5865faa0.akpm@osdl.org>
Date:	Wed, 30 Aug 2006 15:57:10 -0700
From:	Andrew Morton <akpm@...l.org>
To:	piet@...elane.com, vgoyal@...ibm.com,
	George Anzinger <george@...dturkeyranch.net>,
	Discussion
	 "list for crash utility usage, maintenance and development" 
	<crash-utility@...hat.com>, kgdb-bugreport@...ts.sourceforge.net,
	Subhachandra Chandra <schandra@...elane.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] [Crash-utility] Patch to use gdb's bt in crash - works
 great with kgdb! - KGDB in Linus Kernel.

On Wed, 30 Aug 2006 14:48:22 -0700
Andrew Morton <akpm@...l.org> wrote:

>  Plus: I'd want to see a maintainance person or team who
> respond promptly to email and who remain reasonably engaged with what's
> going on in the mainline kernel.  Because if problems crop up (and they
> will), I don't want to have to be the bunny who has to worry about them...

umm, clarification needed here.

No criticism of the present maintainers intended!  Last time I grabbed the
kgdb patches from sf.net they applied nicely, worked quite reliably (much
better than the old ones I'd been trying to sustain) and had been
tremendously cleaned up.

But if we're to move this work from sf.net to kernel.org, the kgdb
maintainers' workload, email load, turnaround time requirements,
bug-difficulty and everything else will go up quite a lot, at least short-term.
If they don't want to volunteer take that on (perfectly legit and sane) then
things should stay as they are.

(otoh, a merge would decrease their patch-maintenance load, and would
increase the number of people who fix things for them, and might attract new
maintainers).

It's a big step.
-
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/