From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 81a448d7b066
Date: Thu, 29 Jul 2021 09:43:02 -0700 [thread overview]
Message-ID: <20210729164302.GL3601443@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. These are the second batch of bug fixes for 5.14; they
should clear up most of the log recovery problems that have been
reported lately.
The new head of the for-next branch is commit:
81a448d7b066 xfs: prevent spoofing of rtbitmap blocks when recovering buffers
New Commits:
Darrick J. Wong (1):
[81a448d7b066] xfs: prevent spoofing of rtbitmap blocks when recovering buffers
Dave Chinner (11):
[b1e27239b916] xfs: flush data dev on external log write
[b5d721eaae47] xfs: external logs need to flush data device
[9d3920644081] xfs: fold __xlog_state_release_iclog into xlog_state_release_iclog
[0dc8f7f139f0] xfs: fix ordering violation between cache flushes and tail updates
[45eddb414047] xfs: factor out forced iclog flushes
[2bf1ec0ff067] xfs: log forces imply data device cache flushes
[8191d8222c51] xfs: avoid unnecessary waits in xfs_log_force_lsn()
[32baa63d82ee] xfs: logging the on disk inode LSN can make it go backwards
[d8f4c2d0398f] xfs: Enforce attr3 buffer recovery order
[b2ae3a9ef911] xfs: need to see iclog flags in tracing
[9d110014205c] xfs: limit iclog tail updates
Code Diffstat:
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-29 16:43 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=20210729164302.GL3601443@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