From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756872Ab0IIBxs (ORCPT ); Wed, 8 Sep 2010 21:53:48 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:53786 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754993Ab0IIBxn (ORCPT ); Wed, 8 Sep 2010 21:53:43 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=w+yCq1VFeUFpHZJbpuDvqjgBWbuskb2NnM/T9T4w1dTrAuLqvBnN3Pi1CI3gfArK9+ jRqVNVNCvFday1w8Yt61UsIvteJEjepQCEzYVqcyrxjQlylWVmGDxA6y1ULzaeHepPP2 tqwdAovnhcSzyZzEotoN5XK0XfOg96+0fZE5Y= Date: Thu, 9 Sep 2010 03:53:52 +0200 From: Frederic Weisbecker To: Andrew Morton Cc: Jarek Poplawski , linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org, Christoph Hellwig , Al Viro Subject: Re: [Bug] possible circular locking in reiserfs_unpack Message-ID: <20100909015346.GA5999@nowhere> References: <20100905113121.GA1876@del.dom.local> <20100908153730.5ad13f71.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100908153730.5ad13f71.akpm@linux-foundation.org> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 08, 2010 at 03:37:30PM -0700, Andrew Morton wrote: > On Sun, 5 Sep 2010 13:31:21 +0200 > Jarek Poplawski wrote: > > > Hi, > > I get this warning on every lilo write with 2.6.35.4 and a bit/git > > later too. > > > > Can you tell us the latest kernel version which did *not* have this > bug? That way we can narrow the problem down a bit. > > Thanks. Ah, when you see &REISERFS_SB(s)->lock in a bug report, don't hesitate to blame me :-) This is a problem resulting from the bkl conversion to a mutex that introduced a lot of new locking dependencies. Most of them have been fixed, but for less tested paths like ioctl, we hear about it later. Does the following patch fixes the issue? If so, I'll make a proper changelog and put the appropriate 2.6.33-35 stable tags for the backport. Thnaks! diff --git a/fs/reiserfs/ioctl.c b/fs/reiserfs/ioctl.c index f53505d..679d502 100644 --- a/fs/reiserfs/ioctl.c +++ b/fs/reiserfs/ioctl.c @@ -188,7 +188,7 @@ int reiserfs_unpack(struct inode *inode, struct file *filp) /* we need to make sure nobody is changing the file size beneath ** us */ - mutex_lock(&inode->i_mutex); + reiserfs_mutex_lock_safe(&inode->i_mutex, inode->i_sb); reiserfs_write_lock(inode->i_sb); write_from = inode->i_size & (blocksize - 1);