Date: Fri, 22 Jun 2012 19:21:27 +0300
From: Touko Korpela <touko.korpela@iki.fi>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH] dm thin: reinstate missing mempool_free in
 cell_release_singleton
Message-ID: <20120622162127.GA19624@lisko>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120622151650.GA5785@kroah.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 933
Lines: 22

Greg KH wrote:
> On Fri, Jun 22, 2012 at 10:59:48AM -0400, Mike Snitzer wrote:
> > Hi Greg,
> > 
> > 3.3-stable pulled in upstream commit
> > 6f94a4c45a6f744383f9f695dde019998db3df55 (dm thin: fix stacked bi_next
> > usage)
> > 
> > But later in the 3.4 development window it was determined that that
> > commit introduced a significant leak.  The following upstream commit
> > fixes it (but unfortunately didn't cc: stable).
>
> 3.3 is end-of-life, so there's not much I can do with the 3.3-stable
> tree anymore, sorry.  If there's any other tree I should apply this to
> that is active (i.e. 3.0 or 3.4), please let me know.

Looks like you forgot 3.2 that is affected (since 3.2.14).
--
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/