All of lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: [GIT PULL] xfs: bug fixes for 5.14-rc4
Date: Sat, 31 Jul 2021 14:37:40 -0700	[thread overview]
Message-ID: <20210731213740.GN3601443@magnolia> (raw)

Hi Linus,

Please pull this branch containing a bunch of bug fixes in XFS.  Dave
and I have been busy the last couple of weeks to find and fix as many
log recovery bugs as we can find; here are the results so far.  Go
fstests -g recoveryloop! ;)

The branch merges cleanly against upstream as of a few minutes ago.
Please let me know if anything else strange happens during the merge
process.

--D

The following changes since commit b102a46ce16fd5550aed882c3c5b95f50da7992c:

  xfs: detect misaligned rtinherit directory extent size hints (2021-07-15 09:58:42 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.14-fixes-2

for you to fetch changes up to 81a448d7b0668ae39c08e6f34a54cc7eafb844f1:

  xfs: prevent spoofing of rtbitmap blocks when recovering buffers (2021-07-29 09:27:29 -0700)

----------------------------------------------------------------
Fixes for 5.14-rc4:
 * Fix a number of coordination bugs relating to cache flushes for
   metadata writeback, cache flushes for multi-buffer log writes, and
   FUA writes for single-buffer log writes.
 * Fix a bug with incorrect replay of attr3 blocks.
 * Fix unnecessary stalls when flushing logs to disk.
 * Fix spoofing problems when recovering realtime bitmap blocks.

----------------------------------------------------------------
Darrick J. Wong (1):
      xfs: prevent spoofing of rtbitmap blocks when recovering buffers

Dave Chinner (11):
      xfs: flush data dev on external log write
      xfs: external logs need to flush data device
      xfs: fold __xlog_state_release_iclog into xlog_state_release_iclog
      xfs: fix ordering violation between cache flushes and tail updates
      xfs: factor out forced iclog flushes
      xfs: log forces imply data device cache flushes
      xfs: avoid unnecessary waits in xfs_log_force_lsn()
      xfs: logging the on disk inode LSN can make it go backwards
      xfs: Enforce attr3 buffer recovery order
      xfs: need to see iclog flags in tracing
      xfs: limit iclog tail updates

 fs/xfs/libxfs/xfs_log_format.h  |  11 +-
 fs/xfs/xfs_buf_item_recover.c   |  15 ++-
 fs/xfs/xfs_inode_item_recover.c |  39 +++++--
 fs/xfs/xfs_log.c                | 251 ++++++++++++++++++++++++++--------------
 fs/xfs/xfs_log_cil.c            |  13 ++-
 fs/xfs/xfs_log_priv.h           |  16 ++-
 fs/xfs/xfs_trace.h              |   5 +-
 7 files changed, 244 insertions(+), 106 deletions(-)

             reply	other threads:[~2021-07-31 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 21:37 Darrick J. Wong [this message]
2021-08-01 19:28 ` [GIT PULL] xfs: bug fixes for 5.14-rc4 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=20210731213740.GN3601443@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --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.