From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org
Cc: dchinner@redhat.com, hch@infradead.org, hch@lst.de, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
mcgrof@kernel.org, ruansy.fnst@fujitsu.com
Subject: [ANNOUNCE] xfs-linux: vfs-6.6-merge updated to ce85a1e04645
Date: Fri, 4 Aug 2023 08:28:11 -0700 [thread overview]
Message-ID: <169116275623.3187159.16862410128731457358.stg-ugh@frogsfrogsfrogs> (raw)
Hi folks,
The vfs-for-next branch of the xfs-linux repository at:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated. This is the long-promised patchset to allow the
kernel to freeze the fs while guaranteeing that userspace cannot
unfreeze the fs; and the first user of that functionality (online fsck).
This will enable Luis' auto-freeze-on-suspend patches, and Shiyang's
pmem pre-removal hook.
The new head of the vfs-for-next branch is commit:
ce85a1e04645 xfs: stabilize fs summary counters for online fsck
3 new commits:
Darrick J. Wong (3):
[880b9577855e] fs: distinguish between user initiated freeze and kernel initiated freeze
[59ba4fdd2d1f] fs: wait for partially frozen filesystems
[ce85a1e04645] xfs: stabilize fs summary counters for online fsck
Code Diffstat:
Documentation/filesystems/vfs.rst | 6 +-
block/bdev.c | 8 +-
fs/f2fs/gc.c | 8 +-
fs/gfs2/super.c | 12 ++-
fs/gfs2/sys.c | 4 +-
fs/ioctl.c | 8 +-
fs/super.c | 113 ++++++++++++++++++++---
fs/xfs/scrub/fscounters.c | 188 ++++++++++++++++++++++++++++++--------
fs/xfs/scrub/scrub.c | 6 +-
fs/xfs/scrub/scrub.h | 1 +
fs/xfs/scrub/trace.h | 26 ++++++
include/linux/fs.h | 15 ++-
12 files changed, 321 insertions(+), 74 deletions(-)
reply other threads:[~2023-08-04 15:29 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=169116275623.3187159.16862410128731457358.stg-ugh@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=dchinner@redhat.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ruansy.fnst@fujitsu.com \
/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).