linux-kernel - Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending

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: <47C6F4F9.90700@zytor.com>
Date:	Thu, 28 Feb 2008 09:52:57 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Klaus S. Madsen" <ksm@...rnemadsen.org>
CC:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending

Klaus S. Madsen wrote:
> 
> Hope this helps. 
> 

What this seems to indicate is a segfault inside VM mode that causes it 
to exit to deliver the SIGSEGV, so without more information, such as 
signal context, there isn't much to know about it.

It looks like the fault happens inside the VESA BIOS, specifically VBE 
function 3:

--------V-104F03-----------------------------
INT 10 - VESA SuperVGA BIOS - GET CURRENT VIDEO MODE
         AX = 4F03h
Return: AL = 4Fh if function supported
         AH = status
             00h successful
                 BX = video mode (see #00083,#00084)
                     bit 13: VBE/AF v1.0P accelerated video mode
                     bit 14: linear frame buffer enabled (VBE v2.0+)
                     bit 15: don't clear video memory
             01h failed
SeeAlso: AH=0Fh,AX=4E04h,AX=4F02h

... which normally would be a trivial function which only reads a couple 
of status words out of internal state and returns.

****

Typically, when the kernel reflects an error in VM86 mode it will update 
the structure in memory (in your case, the vm86plus_struct) to reflect 
the context.  Would it be possible for you to read it out?

[FWIW, that code looks like it's using assembly for no good current 
reason.  Not sure if it'd help to clean it up.]

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