linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 2032a8a27b5c
Date: Wed, 27 Mar 2019 09:55:27 -0700	[thread overview]
Message-ID: <20190327165527.GC1183@magnolia> (raw)

Hi folks,

The for-next branch of the xfs-linux repository at:

	git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git

has just been updated.

Patches often get missed, so please check if your outstanding
patches were in this update. If they have not been in this update,
please resubmit them to linux-xfs@vger.kernel.org so they can be
picked up in the next update.

The new head of the for-next branch is commit:

2032a8a27b5c xfs: serialize unaligned dio writes against all other dio writes

New Commits:

Brian Foster (2):
      [6958d11f77d4] xfs: don't trip over uninitialized buffer on extent read of corrupted inode
      [2032a8a27b5c] xfs: serialize unaligned dio writes against all other dio writes

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


Code Diffstat:

 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-27 16:55 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=20190327165527.GC1183@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).