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

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 1 Sep 2007 13:18:31 +0200
From:	Andi Kleen <ak@...e.de>
To:	"Jan Beulich" <jbeulich@...ell.com>
Cc:	linux-kernel@...r.kernel.org, patches@...-64.org
Subject: Re: [PATCH] x86: optionally show last exception from/to register contents (v2)

On Tuesday 28 August 2007 12:44:31 Jan Beulich wrote:
> .. when dumping register state. This is particularly useful when gcc
> managed to tail-call optimize an indirect call which happens to hit a
> NULL (or otherwise invalid) pointer.

I added it, with a warning in the documentation and changelog

Also all the other patches except for the #DF one. Thanks.

BTW I think there is a reasonable cheap way to avoid the interrupt race: 

If pda->irqcount was split into two 16bit words and irq entry code increases the upper 
16bit word (that should be nearly free because because both are in L1 cache; 
with some luck the CPU can even dual-issue). Then the traps code could save
the irq count early and then in the no_context case disable interrupts,
compare and only print LER if there were no interrupts inbetween.

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