From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755765AbYIDTm5 (ORCPT ); Thu, 4 Sep 2008 15:42:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753280AbYIDTms (ORCPT ); Thu, 4 Sep 2008 15:42:48 -0400 Received: from py-out-1112.google.com ([64.233.166.183]:49734 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753123AbYIDTmr (ORCPT ); Thu, 4 Sep 2008 15:42:47 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=lW1JcG++F7Yx3tG2QibqRHkcydCPa7C8Z3TIzBYluSvpAy8QXl1FWT0KiUcUVYeAqZ 9Tffpz2RZ3GlxTFBNCC/kHoqVsYRFVKBlbedoyqgFLsP6WjXQrfYOXlxhdQUODs/IZCw b4C/OgziODDgvhSqRd/0uwyF92b8qble0IANY= Message-ID: Date: Thu, 4 Sep 2008 21:42:46 +0200 From: "=?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?=" To: "Hugh Dickins" Subject: Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption Cc: "Alan Jenkins" , "Alan Cox" , "Jeremy Fitzhardinge" , "Yinghai Lu" , "Ingo Molnar" , "H. Peter Anvin" , "Linux Kernel Mailing List" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline References: <48B701FB.2020905@goop.org> <86802c440808281849nb972d64te89894077ea9f33c@mail.gmail.com> <48B76CE0.5010309@goop.org> <20080829102547.655440bf@lxorguk.ukuu.org.uk> <48B7E6EE.9090901@tuffmail.co.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by alpha id m84Jh1dq012438 2008/8/29 RafaÅ‚ MiÅ‚ecki :> 2008/8/29 Hugh Dickins :>> Here's my version of Jeremy's patch, that I've now tested on my machines,>> as x86_32 and as x86_64. It addresses none of the points Alan Cox made,>> and it stays silent for me, even after suspend+resume, unless I actually>> introduce corruption myself. Omits Jeremy's check in fault.c, but does>> a check every minute, so should soon detect RafaÅ‚'s HDMI corruption>> without any need to suspend+resume.>> Your periodic test works fine:>> Corrupted low memory at ffff88000000be9c (be9c phys) = b02a0004> [] check_for_bios_corruption+0x93/0x9f> [] ? periodic_check_for_corruption+0x0/0x25> [] periodic_check_for_corruption+0x9/0x25>> By the way I confirmed this bug on Sony Vaio FW11M (my one is FW11S).> Probably more machines from FW11* are affected. If this patch is known to work fine for Sony Vaio FW* and Alan'smachine, could it go mainline somehow? -- RafaÅ‚ MiÅ‚eckiÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ¥Šwÿº{.nÇ+‰·¥Š{±þG«�éÿŠ{ayºʇڙë,j­¢f£¢·hš�ï�êÿ‘êçz_è®(­éšŽŠÝ¢j"�ú¶m§ÿÿ¾«þG«�éÿ¢¸?™¨è­Ú&£ø§~�á¶iO•æ¬z·švØ^¶m§ÿÿà ÿ¶ìÿ¢¸?–I¥