From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: kamal.mostafa@canonical.com
Cc: clm@fb.com, jbacik@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [3.13.y][SRU][PATCH 0/1] btrfs: fix defrag 32-bit integer overflow
Date: Wed, 18 Jun 2014 13:23:53 -0400 [thread overview]
Message-ID: <cover.1403107937.git.joseph.salisbury@canonical.com> (raw)
BugLink: http://bugs.launchpad.net/bugs/1324953
Hello,
Please consider including upstream commit c41570c9 in the next v3.13.y release. It was included upstream as of v3.14-rc2. It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1324953 .
commit c41570c9d29764f797fa35490d72b7395a0105c3
Author: Justin Maggard <jmaggard10@gmail.com>
Date: Tue Jan 21 11:18:29 2014 -0800
btrfs: fix defrag 32-bit integer overflow
This commit is a clean cherry-pick against 3.13.y.
Sincerely,
Joseph Salisbury
Justin Maggard (1):
btrfs: fix defrag 32-bit integer overflow
fs/btrfs/ioctl.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.0.0
next reply other threads:[~2014-06-18 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 17:23 Joseph Salisbury [this message]
2014-06-20 8:00 ` [3.13.y][SRU][PATCH 0/1] btrfs: fix defrag 32-bit integer overflow Jiri Slaby
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=cover.1403107937.git.joseph.salisbury@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=kamal.mostafa@canonical.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.