linux-kernel - Re: [git pull] x86 arch updates for v2.6.25

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: <p73ejbn2xk2.fsf@bingen.suse.de>
Date:	Fri, 08 Feb 2008 18:00:13 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Maxim Levitsky <maximlevitsky@...il.com>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [git pull] x86 arch updates for v2.6.25

Linus Torvalds <torvalds@...ux-foundation.org> writes:
>
> So I'd merge a patch that puts oops information (or the whole console 
> printout) in the Intel management stuff in a heartbeat. That code is 
> likely much grottier than any kgdb thing will ever be (Intel really 
> screwed up the interface and made it some insane XML thing), but it's also 
> fundamentally more important - if it means that normal users can give oops 
> reports after they happened in X (or, these days, probably more commonly 
> during suspend/resume) and the machine just died.

I agree. Even with XML ugliness that's a fairly important area.

> kgdb? Not so interesting. We have many more hard problems happening at 
> user sites, not in developer hands.

The other problem with the current kgdb code is that it has some serious
problems. e.g. it reinvents various kernel interfaces that already
exist -- one example is that it adds new notify_die()s just to reimplement
the standard __ex_table exceptions in a bogus way.
Couple of other issues. So even if it was a good idea to merge the
code is not really fully in merge shape anyways.

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