linux-kernel - Re: + espfix-code-cleanup.patch added to -mm tree

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]

Message-ID: <44CF4B84.6010409@aknet.ru>
Date:	Tue, 01 Aug 2006 16:39:32 +0400
From:	Stas Sergeev <stsp@...et.ru>
To:	Chuck Ebbert <76306.1226@...puserve.com>
Cc:	"akpm@...l.org" <akpm@...l.org>, zach@...are.com,
	rohitseth@...gle.com, JBeulich@...ell.com, ak@....de,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: + espfix-code-cleanup.patch added to -mm tree

Hi.

Chuck Ebbert wrote:
> we are on a ring0 32-bit stack that's not zero-based.  If an exception
> occurs in that state, UNWIND_ESPFIX_STACK restores the proper kernel
> SS and ESP but on return from the exception nothing restores the espfix
> stack.  I guess this isn't a problem now because exceptions in kernel
> mode are fatal but a kernel debugger might have problems here?
Perhaps you are right, but... unless there is some quick
way to mark that part of code "undebuggable", I'll better
leave that for the debugger maintainers to think about.

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