Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761378AbXLTMy7 (ORCPT ); Thu, 20 Dec 2007 07:54:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758915AbXLTMyv (ORCPT ); Thu, 20 Dec 2007 07:54:51 -0500 Received: from ro-out-1112.google.com ([72.14.202.179]:33961 "EHLO ro-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753398AbXLTMyu (ORCPT ); Thu, 20 Dec 2007 07:54:50 -0500 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=EmowBWiIB7vSs+cbJNoyrU8m5DtIDxwFtGAMiw+s70jBLZtnahIiz4P90qFiuDw+ZncrrLb3H7jwA7d9VJyja2anvJZwQTV3Nqb06BOx7e4Wbm3m7LmbrBkxxSDrOVZ6L/iGEVnFX1h8SUveGCQpLfBt7DUpJGi5eI9Ki66SVlw= Message-ID: Date: Thu, 20 Dec 2007 07:54:48 -0500 From: "Miles Lane" To: "David Howells" Subject: Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem") Cc: "Andrew Morton" , LKML , "Ingo Molnar" , "Russell King" In-Reply-To: <5102.1198150640@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4769F409.6030300@gmail.com> <4769FF37.5060308@gmail.com> <20071219220307.d69c0fde.akpm@linux-foundation.org> <5102.1198150640@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1110 Lines: 25 On Dec 20, 2007 6:37 AM, David Howells wrote: > Andrew Morton wrote: > > > I would be suspecting iget-stop-procfs-from-using-iget-and-read_inode.patch. > > I think your suspicions are very unlikely. The patch only affects > proc_get_inode() - and looking at the patch backtrace, it looks like the > system is successfully past that already (it's unlikely that > proc_reg_read+0x60/0x74 would have been reached otherwise). > > If my patch to procfs is wrong, it would affect all proc files and ought be > immediately detectable. I tested the patch Andrew sent. I ran "cat /proc/iomem" before trying a suspend-to-disk. It worked fine. Then I suspended and resumed. This time, "cat /proc/iomem" caused the stack trace to be generated. So, you are right, you patch is not the problem. Thanks, Miles -- 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/