From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de,
fstests <fstests@vger.kernel.org>
Subject: [GIT PULL] xfs: new code for 6.0, part 2
Date: Sat, 13 Aug 2022 08:59:22 -0700 [thread overview]
Message-ID: <YvfKWgGHTQVxBFBe@magnolia> (raw)
Hi Linus,
Please pull this second branch containing new XFS code for 6.0. There's
not a lot time around, just the usual bug fixes and corrections for
missing error returns.
As usual, I did a test-merge with upstream master as of a few minutes
ago, and it completed flawlessly. Please let me know if you encounter
any problems.
--D
The following changes since commit 5e9466a5d0604e20082d828008047b3165592caf:
xfs: delete extra space and tab in blank line (2022-07-31 09:21:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.20-merge-8
for you to fetch changes up to 031d166f968efba6e4f091ff75d0bb5206bb3918:
xfs: fix inode reservation space for removing transaction (2022-08-10 17:43:49 -0700)
----------------------------------------------------------------
New code for 6.0:
- Return error codes from block device flushes to userspace.
- Fix a deadlock between reclaim and mount time quotacheck.
- Fix an unnecessary ENOSPC return when doing COW on a filesystem with
severe free space fragmentation.
- Fix a miscalculation in the transaction reservation computations for
file removal operations.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
----------------------------------------------------------------
Chandan Babu R (1):
xfs: Fix false ENOSPC when performing direct write on a delalloc extent in cow fork
Darrick J. Wong (2):
xfs: check return codes when flushing block devices
xfs: fix intermittent hang during quotacheck
hexiaole (1):
xfs: fix inode reservation space for removing transaction
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(-)
next reply other threads:[~2022-08-13 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 15:59 Darrick J. Wong [this message]
2022-08-13 21:48 ` [GIT PULL] xfs: new code for 6.0, part 2 pr-tracker-bot
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=YvfKWgGHTQVxBFBe@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.