From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] block device inode syncing improvements
Date: Sun, 31 Oct 2021 13:42:32 -0600 [thread overview]
Message-ID: <3017c47b-debe-0108-ddf3-279de7621883@kernel.dk> (raw)
Hi Linus,
On top of the core block branch, this topic branch contains improvements
to how bdev inode syncing is handled, unifying the API.
Please pull!
The following changes since commit 8e9f666a6e66d3f882c094646d35536d2759103a:
blk-crypto: update inline encryption documentation (2021-10-21 10:49:32 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/for-5.16/inode-sync-2021-10-29
for you to fetch changes up to 1e03a36bdff4709c1bbf0f57f60ae3f776d51adf:
block: simplify the block device syncing code (2021-10-22 08:36:55 -0600)
----------------------------------------------------------------
for-5.16/inode-sync-2021-10-29
----------------------------------------------------------------
Christoph Hellwig (7):
fs: remove __sync_filesystem
block: remove __sync_blockdev
xen-blkback: use sync_blockdev
btrfs: use sync_blockdev
fat: use sync_blockdev_nowait
ntfs3: use sync_blockdev_nowait
block: simplify the block device syncing code
block/bdev.c | 28 ++++++++++++-----
drivers/block/xen-blkback/xenbus.c | 2 +-
fs/btrfs/volumes.c | 2 +-
fs/fat/inode.c | 6 ++--
fs/internal.h | 11 -------
fs/ntfs3/inode.c | 2 +-
fs/sync.c | 62 ++++++++++++++------------------------
include/linux/blkdev.h | 9 ++++++
8 files changed, 56 insertions(+), 66 deletions(-)
--
Jens Axboe
next reply other threads:[~2021-10-31 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 19:42 Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-31 19:41 [GIT PULL] block device inode syncing improvements Jens Axboe
2021-11-01 17:28 ` 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=3017c47b-debe-0108-ddf3-279de7621883@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--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 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).