public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next **rebased** to 8723d5ba8bda
Date: Mon, 15 Mar 2021 09:40:44 -0700	[thread overview]
Message-ID: <20210315164044.GD22100@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 rebased.  The patch to avoid inode btree cycle deadlocks
during inode walks requires deferred inode inactivation and I
accidentally committed that into the fixes topic branch.  This /should/
fix all the complaints in Zorro's recent bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=212289

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:

8723d5ba8bda xfs: also reject BULKSTAT_SINGLE in a mount user namespace

New Commits:

Bhaskar Chowdhury (1):
      [08a204387e80] docs: ABI: Fix the spelling oustanding to outstanding in the file sysfs-fs-xfs

Christoph Hellwig (1):
      [8723d5ba8bda] xfs: also reject BULKSTAT_SINGLE in a mount user namespace

Darrick J. Wong (2):
      [b5a08423da9d] xfs: fix quota accounting when a mount is idmapped
      [d336f7ebc650] xfs: force log and push AIL to clear pinned inodes when aborting mount


Code Diffstat:

 Documentation/ABI/testing/sysfs-fs-xfs |  2 +-
 fs/xfs/xfs_inode.c                     | 14 +++---
 fs/xfs/xfs_itable.c                    |  6 +++
 fs/xfs/xfs_mount.c                     | 90 +++++++++++++++++-----------------
 fs/xfs/xfs_symlink.c                   |  3 +-
 5 files changed, 61 insertions(+), 54 deletions(-)

                 reply	other threads:[~2021-03-15 16:41 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=20210315164044.GD22100@magnolia \
    --to=djwong@kernel.org \
    --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