linux-kernel - Re: [PATCH] x86: optionally show last exception from/to register contents

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: <20070813142110.GC3406@bingen.suse.de>
Date:	Mon, 13 Aug 2007 16:21:10 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jan Beulich <jbeulich@...ell.com>
Cc:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org,
	patches@...-64.org
Subject: Re: [PATCH] x86: optionally show last exception from/to register contents

> I though you did, but since I never saw it appear in any release, I posted
> this one...

It's a little different (and somewhat hackish I admit) 
ftp://firstfloor.org/pub/ak/x86_64/debug/last-branch
It has far more overhead than yours of course.

The only way to merge something like that would be dynamic
patching and I was never quite motivated for that.

> So especially with the first concern of yours - is it worth at all rev-ing this
> patch to address the other change requests you voiced?

The patch is useful even with the race, just document somewhere
that it is unreliable (perhaps in the printk itself) and do the
other changes.

I would also suggest to enable it by default.

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