mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bpm@sgi.com (Ben Myers)
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: [GIT PULL] XFS bugfixes for 3.13-rc4
Date: Tue, 10 Dec 2013 13:53:15 -0600 (CST)	[thread overview]
Message-ID: <20131210195315.3F9504266DC@whiskey.americas.sgi.com> (raw)

Hi Linus,

   Please pull these bugfixes for xfs.  There is a security fix for memory
   corruption in xfs_attrlist_by_handle, a fix for trim, and a fix for buffer
   overrun in the agfl when growing filesystems with a v4 superblock.

Thanks,
	Ben

The following changes since commit dc1ccc48159d63eca5089e507c82c7d22ef60839:

  Linux 3.13-rc2 (2013-11-29 12:57:14 -0800)

are available in the git repository at:

  git://oss.sgi.com/xfs/xfs.git tags/xfs-for-linus-v3.13-rc4

for you to fetch changes up to f94c44573e7c22860e2c3dfe349c45f72ba35ad3:

  xfs: growfs overruns AGFL buffer on V4 filesystems (2013-12-10 10:04:27 -0600)

----------------------------------------------------------------
xfs: bugfixes for 3.13-rc4

- fix for buffer overrun in agfl with growfs on v4 superblock
- return EINVAL if requested discard length is less than a block
- fix possible memory corruption in xfs_attrlist_by_handle()

----------------------------------------------------------------
Dan Carpenter (1):
      xfs: underflow bug in xfs_attrlist_by_handle()

Dave Chinner (1):
      xfs: growfs overruns AGFL buffer on V4 filesystems

Jie Liu (1):
      xfs: don't perform discard if the given range length is less than block size

 fs/xfs/xfs_discard.c | 5 +++--
 fs/xfs/xfs_fsops.c   | 6 +++++-
 fs/xfs/xfs_ioctl.c   | 3 ++-
 fs/xfs/xfs_ioctl32.c | 3 ++-
 4 files changed, 12 insertions(+), 5 deletions(-)

                 reply	other threads:[~2013-12-10 19:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131210195315.3F9504266DC@whiskey.americas.sgi.com \
    --to=bpm@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®