From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: david@fromorbit.com, xfs@oss.sgi.com,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH][v3.2.y] xfs: really fix the cursor leak in xfs_alloc_ag_vextent_near
Date: Wed, 30 Jul 2014 12:26:36 -0400 [thread overview]
Message-ID: <53D91CBC.1000901@canonical.com> (raw)
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
Sincerely,
Joseph Salisbury
next reply other threads:[~2014-07-30 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:26 Joseph Salisbury [this message]
2014-08-03 0:49 ` [PATCH][v3.2.y] xfs: really fix the cursor leak in xfs_alloc_ag_vextent_near Ben Hutchings
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=53D91CBC.1000901@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=ben@decadent.org.uk \
--cc=david@fromorbit.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