Date: Wed, 17 Dec 2008 11:56:20 -0800
From: Greg KH <greg@kroah.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>, stable@kernel.org,
        Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [stable] [BUG] Upon hitting ^c, inotify blocks on mutex_lock
Message-ID: <20081217195620.GA25375@kroah.com>
References: <20081213164123.GB7639@flint.arm.linux.org.uk> <20081217194855.GA11188@flint.arm.linux.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081217194855.GA11188@flint.arm.linux.org.uk>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org

On Wed, Dec 17, 2008 at 07:48:56PM +0000, Russell King wrote:
> On Sat, Dec 13, 2008 at 04:41:23PM +0000, Russell King wrote:
> > Today, having had gthumb running for a while, I hit ^c expecting it to
> > quit.  The result was a process with zero VSZ and RSS, and it sitting
> > in run state.  Only possible recovery action seems to be a reboot.
> 
> Al Viro looked into this, and suggested that 711a49a might fix the
> problem.  I've just tested this on top of 2.6.27.8, and it does
> indeed appear to fix the problem.  Suggest it should be included
> in the next stable kernel.

It's already queued up for the 2.6.27.10 release to be happening
tomorrow :)

thanks,

greg k-h
--
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/