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 595189c25c28
Date: Thu, 19 Nov 2020 09:51:27 -0800	[thread overview]
Message-ID: <20201119175127.GE9695@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.  This is still bug fixes, maybe I'll get to 5.11 next
week...

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

595189c25c28 xfs: return corresponding errcode if xfs_initialize_perag() fail

New Commits:

Darrick J. Wong (4):
      [e95b6c3ef131] xfs: fix the minrecs logic when dealing with inode root child blocks
      [498fe261f0d6] xfs: strengthen rmap record flags checking
      [6b48e5b8a20f] xfs: directory scrub should check the null bestfree entries too
      [27c14b5daa82] xfs: ensure inobt record walks always make forward progress

Gao Xiang (1):
      [ada49d64fb35] xfs: fix forkoff miscalculation related to XFS_LITINO(mp)

Yu Kuai (1):
      [595189c25c28] xfs: return corresponding errcode if xfs_initialize_perag() fail


Code Diffstat:

 fs/xfs/libxfs/xfs_attr_leaf.c |  8 +++++++-
 fs/xfs/scrub/bmap.c           |  8 ++++----
 fs/xfs/scrub/btree.c          | 45 ++++++++++++++++++++++++++-----------------
 fs/xfs/scrub/dir.c            | 27 +++++++++++++++++++-------
 fs/xfs/xfs_iwalk.c            | 27 +++++++++++++++++++++++---
 fs/xfs/xfs_mount.c            | 11 ++++++++---
 6 files changed, 90 insertions(+), 36 deletions(-)

                 reply	other threads:[~2020-11-19 17:51 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=20201119175127.GE9695@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