From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfsprogs: for-next updated to a68dabd45
Date: Fri, 17 Mar 2023 11:53:29 +0100 [thread overview]
Message-ID: <20230317105329.cp3r7tjquk3svkwx@andromeda> (raw)
Hello.
The xfsprogs for-next branch, located at:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/refs/?h=for-next
Has just been updated.
This contains a libxfs-sync with Linux 6.2.
This should become xfsprogs-6.2 which I plan to release next week, unless
something critical come along.
Patches often get missed, so if your outstanding patches are properly reviewed on
the list and not included in this update, or you have any other question, please
let me know.
The new head of the for-next branch is commit:
a68dabd45f3591456ecf7e35f6a6077db79f6bc6
15 new commits:
Darrick J. Wong (11):
[c3fce4f9b] mkfs: check dirent names when reading protofile
[fb22e1b1b] mkfs: use suboption processing for -p
[e0aeb0581] mkfs: substitute slashes with spaces in protofiles
[b7b81f336] xfs_repair: fix incorrect dabtree hashval comparison
[4f82f9218] xfs_db: fix complaints about unsigned char casting
[9061d756b] xfs: add debug knob to slow down writeback for fun
[fb084f350] xfs: add debug knob to slow down write for fun
[d1dca9f6b] xfs: hoist refcount record merge predicates
[b445624f0] xfs: estimate post-merge refcounts correctly
[88765eda1] xfs: invalidate xfs_bufs when allocating cow extents
[a68dabd45] xfs: fix off-by-one error in xfs_btree_space_to_height
Dave Chinner (2):
[1dcdf5051] xfs: use iomap_valid method to detect stale cached iomaps
[d712be6a9] xfs: drop write error injection is unfixable, remove it
Guo Xuenan (1):
[f5ef81288] xfs: get rid of assert from xfs_btree_islastblock
Jason A. Donenfeld (1):
[9a046f967] treewide: use get_random_u32_below() instead of deprecated function
Code Diffstat:
db/namei.c | 4 +-
io/inject.c | 2 +
libxfs/libxfs_priv.h | 2 +-
libxfs/xfs_alloc.c | 2 +-
libxfs/xfs_bmap.c | 8 ++-
libxfs/xfs_btree.c | 7 ++-
libxfs/xfs_btree.h | 1 -
libxfs/xfs_errortag.h | 18 +++---
libxfs/xfs_ialloc.c | 2 +-
libxfs/xfs_refcount.c | 146 +++++++++++++++++++++++++++++++++++++++++++------
man/man8/mkfs.xfs.8.in | 32 +++++++++--
mkfs/proto.c | 37 ++++++++++++-
mkfs/proto.h | 3 +-
mkfs/xfs_mkfs.c | 72 +++++++++++++++++++++---
repair/da_util.c | 2 +-
15 files changed, 288 insertions(+), 50 deletions(-)
--
Carlos Maiolino
reply other threads:[~2023-03-17 10:53 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=20230317105329.cp3r7tjquk3svkwx@andromeda \
--to=cem@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;
as well as URLs for NNTP newsgroup(s).