From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NAlPo-0002LG-Cj for qemu-devel@nongnu.org; Wed, 18 Nov 2009 09:21:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NAlPj-0002Jg-5U for qemu-devel@nongnu.org; Wed, 18 Nov 2009 09:21:47 -0500 Received: from [199.232.76.173] (port=44056 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAlPh-0002JO-Jm for qemu-devel@nongnu.org; Wed, 18 Nov 2009 09:21:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:63907) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NAlPh-0000GH-8f for qemu-devel@nongnu.org; Wed, 18 Nov 2009 09:21:41 -0500 Message-ID: <4B0402EE.6070609@redhat.com> Date: Wed, 18 Nov 2009 16:21:34 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU References: <4AFBEF9A.5010802@redhat.com> <20091114194745.GA12007@morn.localdomain> <4B01555B.1030109@redhat.com> <4B015B6C.4090000@redhat.com> <20091117022620.GA25962@morn.localdomain> <20091118093949.GA18543@redhat.com> <4B03FB9C.8040407@redhat.com> <20091118141949.GA3193@redhat.com> In-Reply-To: <20091118141949.GA3193@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel@nongnu.org, Glauber Costa , Kevin O'Connor , gpxe@etherboot.org, Naphtali Sprei On 11/18/2009 04:19 PM, Gleb Natapov wrote: >>> >>> Do we have the same problem with tpr patching rom (vapic,bin)? It modifies >>> itself too. >>> >> But a reset will reload it. >> >> > Correct, but Kevin says "sendkey ctrl-alt-delete" jumps to SeaBIOS's > reboot vector without issuing system reset. I am talking about this situation. > That's only if we're in the bios. If an OS has taken over, it will issue a proper reset. If an OS has not taken over (DOS won't, probably) then it isn't Windows and the vapic payload hasn't had a chance to modify itself. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.