From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756362Ab1FUWV0 (ORCPT ); Tue, 21 Jun 2011 18:21:26 -0400 Received: from mta21.charter.net ([216.33.127.81]:35620 "EHLO mta21.charter.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751613Ab1FUWVX (ORCPT ); Tue, 21 Jun 2011 18:21:23 -0400 X-Authority-Analysis: v=1.1 cv=1b2X7W/SifksZeClH/haT1SUt4udqxFGF00pZw2/jJk= c=1 sm=1 a=p9YancsnzTcA:10 a=8DFDbwKGSZsA:10 a=0xc6OLWX_2kA:10 a=8nJEP1OIZ-IA:10 a=xzrYXqw+0zwiO4gHSXHcAg==:17 a=n6QB8HQGw4dP2UgOK_EA:9 a=wPNLvfGTeEIA:10 a=xzrYXqw+0zwiO4gHSXHcAg==:117 Message-ID: <4E01195F.8040000@gregd.org> Date: Tue, 21 Jun 2011 17:21:19 -0500 From: Greg Dietsche User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11 MIME-Version: 1.0 To: Al Viro CC: "linux-kernel@vger.kernel.org" , linux-fsdevel@vger.kernel.org Subject: Re: 3.0 rc3 bug & warning fs/inode.c && fs/fs-writeback.c References: <4E008DD0.2090809@gregd.org> <20110621124556.GZ11521@ZenIV.linux.org.uk> In-Reply-To: <20110621124556.GZ11521@ZenIV.linux.org.uk> 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 On 06/21/2011 07:45 AM, Al Viro wrote: > On Tue, Jun 21, 2011 at 07:25:52AM -0500, Greg Dietsche wrote: >> from the just missed rc4 department: >> I recieved this BUG last night on my laptop and it was shortly >> followed by a warning from the kernel. I doubt that I can reproduce >> this. It happened under a light load. I was doing some emailing >> using thunderbird (er.... icedove.....). let me know if there's >> anything I can do to help debug or if there's more info I can get >> that would help you figure out what went wrong. > > Which filesystems had been mounted? That looks like a stray pointer > to struct inode (i.e. outliving the inode eviction on final iput()); > might be the one fixed by commit 50338b889dc504c69e0cb316ac92d1b9e51f3c8a, > might be something else... > I'm leaning towards might be something else. Correct me if I'm wrong, but it seems that 50338b889dc504c69e0cb316ac92d1b9e51f3c8a was included in rc3. thanks, Greg