linux-kernel - Re: [Xen-devel] Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt ops callsites to make them patchable

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.0703201644490.6730@woody.linux-foundation.org>
Date:	Tue, 20 Mar 2007 16:51:19 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andi Kleen <ak@...e.de>
cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, jeremy@...p.org,
	xen-devel@...ts.xensource.com, netdev@...r.kernel.org,
	mingo@...e.hu, jbeulich@...ell.com,
	virtualization@...ts.linux-foundation.org, chrisw@...s-sol.org,
	virtualization@...ts.osdl.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>, anthony@...emonkey.ws,
	akpm@...ux-foundation.org, David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] Re: [patch 13/26] Xen-paravirt_ops: Consistently
 wrap paravirt ops callsites to make them patchable



On Tue, 20 Mar 2007, Andi Kleen wrote:
> 
> Linus is worried about the unwinder crashing -- that wouldn't help with that.

And to make it clear: this is not a theoretical worry. It happened many 
times over the months the unwinder was in. 

It was supposed to help debugging, but it made bugs that *would* have been 
nicely debuggable without it into nightmares. So the only reason for it 
existing in the first place was actually the thing that made it not work.

		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/