From mboxrd@z Thu Jan  1 00:00:00 1970
From: Carsten Otte <cotte@freenet.de>
Subject: Re: [PATCH] ext3 [linux-2.6.2.]: accessing already freed inodes when under memory pressure
Date: Thu, 19 Feb 2004 21:28:06 +0100
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <200402192128.12923.cotte@freenet.de>
References: <200402191321.39592.cotte@freenet.de> <1077212393.2070.571.camel@sisko.scot.redhat.com> <20040219104905.7d87f351.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Cc: torvalds@osdl.org, linux-fsdevel@vger.kernel.org,
	schwidefsky@de.ibm.com, cotte@de.ibm.com, sct@redhat.com
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mout0.freenet.de ([194.97.50.131]:46028 "EHLO mout0.freenet.de")
	by vger.kernel.org with ESMTP id S267548AbUBSUYi convert rfc822-to-8bit
	(ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 19 Feb 2004 15:24:38 -0500
To: Andrew Morton <akpm@osdl.org>,
	"Stephen C. Tweedie" <sct@redhat.com>
In-Reply-To: <20040219104905.7d87f351.akpm@osdl.org>
Content-Description: clearsigned data
Content-Disposition: inline
List-Id: linux-fsdevel.vger.kernel.org

Am Donnerstag 19 Februar 2004 19:49 schrieb Andrew Morton:
> There are a lot of places where we don't actually hold inode->i_sem while
> diddling inode->i_nlink: ext3_unlink, ext3_rename, others.
>
> hmm, I wonder if that could be it?  If the inode is hardlinked into a
> different directory then the parent dir's i_sem gives us no i_nlink
> protection.
>
> Carsten, are you aware of a particular workload which triggers this?
So far not, all I know is the symptom and a probable cause may be the 
sys_unlink path. I will try to dig that direction with another debugging 
patch tomorrow.