Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756849AbYGNQI6 (ORCPT ); Mon, 14 Jul 2008 12:08:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754278AbYGNQIu (ORCPT ); Mon, 14 Jul 2008 12:08:50 -0400 Received: from il.qumranet.com ([212.179.150.194]:58592 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753351AbYGNQIt (ORCPT ); Mon, 14 Jul 2008 12:08:49 -0400 Message-ID: <487B7A10.9050104@qumranet.com> Date: Mon, 14 Jul 2008 19:08:48 +0300 From: Avi Kivity User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Linus Torvalds CC: Ingo Molnar , Linux Kernel Mailing List , Andrew Morton Subject: Re: [git pull] core, x86: make LIST_POISON less deadly References: <20080714144828.GA22666@elte.hu> <20080714151247.GA27145@elte.hu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 804 Lines: 22 Linus Torvalds wrote: >> We dont do any instruction decoding in #GP handlers to figure out what >> happened, while in the pagefault case we know which address faulted, >> etc. >> > > Why would we care? It would be very obvious from the instruction > disassembly plus the register contents. No need to decode instructions. > We could add a printk to the #GP handler that alerts the reader that a poisoned list is suspected, if we find the address pattern in one of the registers. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/