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: <20070320213918.116862be@lxorguk.ukuu.org.uk>
Date:	Tue, 20 Mar 2007 21:39:18 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andi Kleen <ak@...e.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>, jeremy@...p.org,
	xen-devel@...ts.xensource.com, netdev@...r.kernel.org,
	mingo@...e.hu, Andi Kleen <ak@...e.de>, 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

> > Because that's really the issue: do you want a "pretty" backtrace, or do 
> > you want one that is rock solid but has some crud in it.
> 
> I just want an as exact backtrace as possible. I also think
> that we can make the unwinder robust enough.

Any reason you can't put the exact back trace in "[xxx]" and the ones we
see on the stack which dont look like call trace as ?xxx? It makes the
code a bit trickier but we depend on the quality of traces

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