All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: torvalds@linux-foundation.org
Cc: Dave Chinner <david@fromorbit.com>,
	linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
	sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: bug fixes for 5.1-rc3
Date: Fri, 29 Mar 2019 06:33:11 -0700	[thread overview]
Message-ID: <20190329133311.GD18833@magnolia> (raw)

Hi Linus,

Here are a few fixes for some corruption bugs and uninitialized variable
problems.  The few patches here have gone through a few days worth of
fstest runs with no new problems observed; and they merge cleanly with
master as of a few hours ago.  Please let me know if you encounter any
problems merging them.

--D

The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:

  Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.1-fixes-1

for you to fetch changes up to 2032a8a27b5cc0f578d37fa16fa2494b80a0d00a:

  xfs: serialize unaligned dio writes against all other dio writes (2019-03-26 08:37:55 -0700)

----------------------------------------------------------------
Changes since last update:
- Fix a bunch of static checker complaints about uninitialized variables
  and insufficient range checks.
- Avoid a crash when incore extent map data are corrupt.
- Disallow FITRIM when we haven't recovered the log and know the
  metadata are stale.
- Fix a data corruption when doing unaligned overlapping dio writes.

----------------------------------------------------------------
Brian Foster (2):
      xfs: don't trip over uninitialized buffer on extent read of corrupted inode
      xfs: serialize unaligned dio writes against all other dio writes

Darrick J. Wong (4):
      xfs: dabtree scrub needs to range-check level
      xfs: fix btree scrub checking with regards to root-in-inode
      xfs: always init bma in xfs_bmapi_write
      xfs: prohibit fstrim in norecovery mode

 fs/xfs/libxfs/xfs_bmap.c | 15 +++++++++------
 fs/xfs/scrub/btree.c     | 11 ++++++++++-
 fs/xfs/scrub/dabtree.c   |  5 +++++
 fs/xfs/xfs_discard.c     |  8 ++++++++
 fs/xfs/xfs_file.c        | 27 +++++++++++++++++----------
 5 files changed, 49 insertions(+), 17 deletions(-)

             reply	other threads:[~2019-03-29 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 13:33 Darrick J. Wong [this message]
2019-03-29 21:50 ` [GIT PULL] xfs: bug fixes for 5.1-rc3 pr-tracker-bot

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=20190329133311.GD18833@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --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 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.