From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Artem B. Bityuckiy" Subject: Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between Date: Wed, 27 Apr 2005 20:19:08 +0400 Message-ID: <1114618748.12617.23.camel@sauron.oktetlabs.ru> References: <1114607741.12617.4.camel@sauron.oktetlabs.ru> Reply-To: dedekind@infradead.org Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, dwmw2@infradead.org, viro@math.psu.edu, linux-fsdevel@vger.kernel.org, akpm@osdl.org Return-path: Received: from [213.170.72.194] ([213.170.72.194]:29419 "EHLO shelob.oktetlabs.ru") by vger.kernel.org with ESMTP id S261780AbVD0QTK (ORCPT ); Wed, 27 Apr 2005 12:19:10 -0400 To: Miklos Szeredi In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org =F7 =F3=D2=C4, 27/04/2005 =D7 17:57 +0200, Miklos Szeredi =D0=C9=DB=C5=D4= : > On second thought a wake_up_inode() seems to be missing in > dispose_list() just before destroy_inode(). =20 Good point, thanks. > Also I'm not sure delaying removal from i_sb_list is the right thing. > generic_delete_inode() does this before clear_inode(). As I can see, dispose_list() doesn't correlate with generic_delete_inod= e () code path, so this mustn't be a problem. What am I supposed to do next? I already sent the old patch with the error to Andrew Morton. Should I notify him about this? Just resend? Whatever? Cheers, Artem. --=20 Best Regards, Artem B. Bityuckiy, St.-Petersburg, Russia. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html