From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfsprogs: for-next updated to e05d65121
Date: Wed, 28 Jun 2023 16:14:41 +0200 [thread overview]
Message-ID: <20230628141441.j6n7anpsxamw5pay@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.
Patches often get missed, so if your outstanding patches are properly reviewed on
the list and not included in this update, please let me know.
The new head of the for-next branch is commit:
e05d65121e7dc97a2b010d87514187fec28e4eb4
10 new commits:
Darrick J. Wong (10):
[5a9c316e3] xfs_repair: don't spray correcting imap all by itself
[61872b1b2] xfs_repair: don't log inode problems without printing resolution
[3668ccd82] xfs_repair: fix messaging when shortform_dir2_junk is called
[42453d22a] xfs_repair: fix messaging in longform_dir2_entry_check_data
[54f51a36c] xfs_repair: fix messaging when fixing imap due to sparse cluster
[ceec18a22] xfs_repair: don't add junked entries to the rebuilt directory
[3f734ce4c] xfs_repair: always perform extended xattr checks on uncertain inodes
[36f558c4f] xfs_repair: check low keys of rmap btrees
[144a92750] xfs_repair: warn about unwritten bits set in rmap btree keys
[e05d65121] xfs_db: expose the unwritten flag in rmapbt keys
Code Diffstat:
db/btblock.c | 4 ++++
repair/dino_chunks.c | 14 ++++++------
repair/phase6.c | 46 ++++++++++++++++++----------------------
repair/scan.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++-
4 files changed, 90 insertions(+), 34 deletions(-)
--
Carlos
reply other threads:[~2023-06-28 14:14 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=20230628141441.j6n7anpsxamw5pay@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