public inbox for linux-xfs@vger.kernel.org
 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 125eac243806
Date: Thu, 27 Aug 2020 09:00:30 -0700	[thread overview]
Message-ID: <20200827160030.GV6096@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.  We're still in the stabilization phase for 5.9, and I
wanted to get the fix for the <cough> nasty xattr bug moving asap.

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

125eac243806 xfs: initialize the shortform attr header padding entry

New Commits:

Brian Foster (2):
      [9c516e0e4554] xfs: finish dfops on every insert range shift iteration
      [657f101930bc] xfs: fix off-by-one in inode alloc block reservation calculation

Darrick J. Wong (1):
      [125eac243806] xfs: initialize the shortform attr header padding entry

Eric Sandeen (1):
      [f4020438fab0] xfs: fix boundary test in xfs_attr_shortform_verify


Code Diffstat:

 fs/xfs/libxfs/xfs_attr_leaf.c   | 8 +++++---
 fs/xfs/libxfs/xfs_ialloc.c      | 4 ++--
 fs/xfs/libxfs/xfs_trans_space.h | 2 +-
 fs/xfs/xfs_bmap_util.c          | 2 +-
 4 files changed, 9 insertions(+), 7 deletions(-)

                 reply	other threads:[~2020-08-27 16:00 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=20200827160030.GV6096@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