Re: [PATCH] dm thin: reinstate missing mempool_free incell_release_singleton

[Greg KH]

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.

sorry,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/