Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to 9f187ba0d517
Date: Mon, 31 Oct 2022 09:30:15 -0700	[thread overview]
Message-ID: <Y1/4F6d02GjCfYnq@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 second update contains bugfixes for log recovery
so that they can get wider testing in for-next.  There will be a third
update in a day or two with the fixes for infinite loops in the refcount
processing code.

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

9f187ba0d517 Merge tag 'fix-log-recovery-misuse-6.1_2022-10-31' of git://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into xfs-6.1-fixes

9 new commits:

Darrick J. Wong (9):
      [59da7ff49d67] xfs: fix validation in attr log item recovery
      [a38ebce1da27] xfs: fix memcpy fortify errors in BUI log format copying
      [a38935c03c79] xfs: fix memcpy fortify errors in CUI log format copying
      [b45ca961e946] xfs: fix memcpy fortify errors in RUI log format copying
      [03a7485cd701] xfs: fix memcpy fortify errors in EFI log format copying
      [3c5aaaced999] xfs: refactor all the EFI/EFD log item sizeof logic
      [921ed96b4f4e] xfs: actually abort log recovery on corrupt intent-done log items
      [950f0d50ee71] xfs: dump corrupt recovered log intent items to dmesg consistently
      [9f187ba0d517] Merge tag 'fix-log-recovery-misuse-6.1_2022-10-31' of git://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into xfs-6.1-fixes

Code Diffstat:

 fs/xfs/libxfs/xfs_log_format.h | 60 ++++++++++++++++++++++++---
 fs/xfs/xfs_attr_item.c         | 67 +++++++++++++++---------------
 fs/xfs/xfs_bmap_item.c         | 54 ++++++++++++------------
 fs/xfs/xfs_extfree_item.c      | 94 ++++++++++++++++++++----------------------
 fs/xfs/xfs_extfree_item.h      | 16 +++++++
 fs/xfs/xfs_ondisk.h            | 23 +++++++++--
 fs/xfs/xfs_refcount_item.c     | 57 +++++++++++++------------
 fs/xfs/xfs_rmap_item.c         | 70 ++++++++++++++++---------------
 fs/xfs/xfs_super.c             | 12 ++----
 9 files changed, 266 insertions(+), 187 deletions(-)

                 reply	other threads:[~2022-10-31 16:31 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=Y1/4F6d02GjCfYnq@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