public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>
Subject: [GIT PULL] xfs: fixes for 4.13-rc3
Date: Fri, 28 Jul 2017 12:35:06 -0700	[thread overview]
Message-ID: <20170728193506.GA4477@magnolia> (raw)

Hi Linus,

Here's the first batch of bug fixes for 4.13.

--Darrick

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.13-fixes-2

for you to fetch changes up to 5b094d6dac0451ad89b1dc088395c7b399b7e9e8:

  xfs: fix multi-AG deadlock in xfs_bunmapi (2017-07-26 08:20:03 -0700)

----------------------------------------------------------------
Changes since last update:
- Fix firstfsb variables that we left uninitialized, which could lead to
  locking problems.
- Check for NULL metadata buffer pointers before using them.
- Don't allow btree cursor manipulation if the btree block is corrupt.
  Better to just shut down.
- Fix infinite loop problems in quotacheck.
- Fix buffer overrun when validating directory blocks.
- Fix deadlock problem in bunmapi.

----------------------------------------------------------------
Brian Foster (1):
      xfs: fix quotacheck dquot id overflow infinite loop

Christoph Hellwig (1):
      xfs: fix multi-AG deadlock in xfs_bunmapi

Darrick J. Wong (4):
      xfs: check _btree_check_block value
      xfs: set firstfsb to NULLFSBLOCK before feeding it to _bmapi_write
      xfs: check _alloc_read_agf buffer pointer before using
      xfs: check that dir block entries don't off the end of the buffer

 fs/xfs/libxfs/xfs_bmap.c      | 21 +++++++++++++++++++++
 fs/xfs/libxfs/xfs_btree.c     |  6 ++++--
 fs/xfs/libxfs/xfs_dir2_data.c |  4 ++++
 fs/xfs/libxfs/xfs_refcount.c  |  4 ++++
 fs/xfs/xfs_qm.c               |  3 +++
 fs/xfs/xfs_reflink.c          |  4 +++-
 6 files changed, 39 insertions(+), 3 deletions(-)

                 reply	other threads:[~2017-07-28 19:35 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=20170728193506.GA4477@magnolia \
    --to=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox