From: Ben Hutchings <ben@decadent.org.uk>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: david@fromorbit.com, xfs@oss.sgi.com,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v3.2.y] xfs: really fix the cursor leak in xfs_alloc_ag_vextent_near
Date: Sun, 03 Aug 2014 01:49:47 +0100 [thread overview]
Message-ID: <1407026987.30258.60.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <53D91CBC.1000901@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
On Wed, 2014-07-30 at 12:26 -0400, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> e3a746f5aab71f2dd0a83116772922fb37ae29d6 in the next v3.2.y release. It
> was included in the mainline tree as of v3.5. It has been tested and
> confirmed
> to resolve http://bugs.launchpad.net/bugs/1327360 .
>
>
> commit e3a746f5aab71f2dd0a83116772922fb37ae29d6
> Author: Dave Chinner <dchinner@redhat.com>
> Date: Thu Jul 12 07:40:42 2012 +1000
>
> xfs: really fix the cursor leak in xfs_alloc_ag_vextent_near
I assume I'm supposed to apply this first:
commit 76d095388b040229ea1aad7dea45be0cfa20f589
Author: Dave Chinner <dchinner@redhat.com>
Date: Tue Jun 12 14:20:26 2012 +1000
xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near
So I've queued up both of these.
Ben.
--
Ben Hutchings
Kids! Bringing about Armageddon can be dangerous. Do not attempt it in
your own home. - Terry Pratchett and Neil Gaiman, `Good Omens'
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2014-08-03 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:26 Joseph Salisbury
2014-08-03 0:49 ` Ben Hutchings [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1407026987.30258.60.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=david@fromorbit.com \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®