[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120127221846.GA32654@suse.de>
Date: Fri, 27 Jan 2012 14:18:46 -0800
From: Greg KH <gregkh@...e.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: Dan Magenheimer <dan.magenheimer@...cle.com>,
linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
Seth Jennings <sjenning@...ux.vnet.ibm.com>,
Nitin Gupta <ngupta@...are.org>
Subject: Re: [PATCH] zcache: fix deadlock condition
On Fri, Jan 27, 2012 at 03:39:28PM -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 25, 2012 at 02:32:51PM -0800, Dan Magenheimer wrote:
> > I discovered this deadlock condition awhile ago working on RAMster
> > but it affects zcache as well. The list spinlock must be
> > locked prior to the page spinlock and released after. As
> > a result, the page copy must also be done while the locks are held.
> >
> > Applies to 3.2. Konrad, please push (via GregKH?)...
> > this is definitely a bug fix so need not be pushed during
> > a -rc0 window.
>
> Looks good to me. Greg, could you apply the patch to your tree
> please? [Or would you rather I sent an GIT pull?]
I will queue it up, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists