mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL for v6.11] vfs iomap
Date: Fri, 12 Jul 2024 16:03:24 +0200	[thread overview]
Message-ID: <20240712-vfs-iomap-8b6a04cb891d@brauner> (raw)

Hey Linus,

/* Summary */
This contains some minor work for the iomap subsystem:

- Add documentaiton on the design of iomap and how to port to it.

- Optimize iomap_read_folio().

- Bring back the change to iomap_write_end() to no increase i_size. This is
  accompanied by a change to xfs to reserve blocks for truncating large
  realtime inodes to avoid exposing stale data when iomap_write_end()
  stops increasing i_size.

/* Testing */
clang: Debian clang version 16.0.6 (26)
gcc: (Debian 13.2.0-24)

All patches are based on v6.10-rc4 and have been sitting in linux-next.
No build failures or warnings were observed.

/* Conflicts */
No known conflicts.

The following changes since commit 6ba59ff4227927d3a8530fc2973b80e94b54d58f:

  Linux 6.10-rc4 (2024-06-16 13:40:16 -0700)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11.iomap

for you to fetch changes up to 602f09f4029c7b5e1a2f44a7651ac8922a904a1b:

  iomap: don't increase i_size in iomap_write_end() (2024-06-19 15:58:28 +0200)

Please consider pulling these changes from the signed vfs-6.11.iomap tag.

Thanks!
Christian

----------------------------------------------------------------
vfs-6.11.iomap

----------------------------------------------------------------
Darrick J. Wong (1):
      Documentation: the design of iomap and how to port

Ritesh Harjani (IBM) (1):
      iomap: Optimize iomap_read_folio

Zhang Yi (2):
      xfs: reserve blocks for truncating large realtime inode
      iomap: don't increase i_size in iomap_write_end()

 Documentation/filesystems/index.rst            |   1 +
 Documentation/filesystems/iomap/design.rst     | 441 +++++++++++++++
 Documentation/filesystems/iomap/index.rst      |  13 +
 Documentation/filesystems/iomap/operations.rst | 713 +++++++++++++++++++++++++
 Documentation/filesystems/iomap/porting.rst    | 120 +++++
 MAINTAINERS                                    |   1 +
 fs/iomap/buffered-io.c                         |  73 ++-
 fs/xfs/xfs_iops.c                              |  15 +-
 8 files changed, 1351 insertions(+), 26 deletions(-)
 create mode 100644 Documentation/filesystems/iomap/design.rst
 create mode 100644 Documentation/filesystems/iomap/index.rst
 create mode 100644 Documentation/filesystems/iomap/operations.rst
 create mode 100644 Documentation/filesystems/iomap/porting.rst

             reply	other threads:[~2024-07-12 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 14:03 Christian Brauner [this message]
2024-07-15 20:34 ` 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=20240712-vfs-iomap-8b6a04cb891d@brauner \
    --to=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®