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 updated to 031d166f968e
Date: Thu, 11 Aug 2022 09:04:59 -0700	[thread overview]
Message-ID: <YvUoq3UIolkCQLcx@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 the last of the bugfixes before I hand things
over to Dave on Sunday.

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

031d166f968e xfs: fix inode reservation space for removing transaction

4 new commits:

Chandan Babu R (1):
      [d62113303d69] xfs: Fix false ENOSPC when performing direct write on a delalloc extent in cow fork

Darrick J. Wong (2):
      [7d839e325af2] xfs: check return codes when flushing block devices
      [f0c2d7d2abca] xfs: fix intermittent hang during quotacheck

hexiaole (1):
      [031d166f968e] xfs: fix inode reservation space for removing transaction

Code Diffstat:

 fs/xfs/libxfs/xfs_trans_resv.c |   2 +-
 fs/xfs/xfs_file.c              |  22 +++--
 fs/xfs/xfs_log.c               |  12 ++-
 fs/xfs/xfs_qm.c                |   5 ++
 fs/xfs/xfs_reflink.c           | 198 +++++++++++++++++++++++++++++++++--------
 5 files changed, 193 insertions(+), 46 deletions(-)

                 reply	other threads:[~2022-08-11 16:24 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=YvUoq3UIolkCQLcx@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