linux-kernel - Re: [patch] i386: show_registers(): try harder to print failing code

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]

Date:	Wed, 19 Jul 2006 00:12:32 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Chuck Ebbert" <76306.1226@...puserve.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...l.org>,
	"Linus Torvalds" <torvalds@...l.org>, "Andi Kleen" <ak@...e.de>
Subject: Re: [patch] i386: show_registers(): try harder to print failing code

On 18/07/06, Chuck Ebbert <76306.1226@...puserve.com> wrote:
> show_registers() tries to dump failing code starting 43 bytes
> before the offending instruction, but this address can be bad,
> for example in a device driver where the failing instruction is
> less than 43 bytes from the start of the driver's code.  When that
> happens, try to dump code starting at the failing instruction
> instead of printing no code at all.
>
Shouldn't the kernel be printing some info noting that this fallback
is in use then? Or will that be completely obvious and I'm just not
able to see that?

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
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/