linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	rgoldwyn@suse.de
Subject: [ANNOUNCE] xfs-linux: iomap-5.10-merge updated to 1a31182edd00
Date: Mon, 28 Sep 2020 09:11:17 -0700	[thread overview]
Message-ID: <20200928161117.GA49524@magnolia> (raw)

Hi folks,

The iomap-5.10-merge 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.  Hopefully this is it for 5.10...

The new head of the iomap-5.10-merge branch is commit:

1a31182edd00 iomap: Call inode_dio_end() before generic_write_sync()

New Commits:

Andreas Gruenbacher (1):
      [c114bbc6c423] iomap: Fix direct I/O write consistency check

Christoph Hellwig (1):
      [c3d4ed1abecf] iomap: Allow filesystem to call iomap_dio_complete without i_rwsem

Goldwyn Rodrigues (1):
      [1a31182edd00] iomap: Call inode_dio_end() before generic_write_sync()

Matthew Wilcox (Oracle) (12):
      [e6e7ca92623a] iomap: Clear page error before beginning a write
      [14284fedf59f] iomap: Mark read blocks uptodate in write_begin
      [7ed3cd1a69e3] iomap: Fix misplaced page flushing
      [24addd848a45] fs: Introduce i_blocks_per_page
      [a6901d4d148d] iomap: Use kzalloc to allocate iomap_page
      [b21866f514cb] iomap: Use bitmap ops to set uptodate bits
      [0a195b91e899] iomap: Support arbitrarily many blocks per page
      [7d636676d284] iomap: Convert read_count to read_bytes_pending
      [0fb2d7209d66] iomap: Convert write_count to write_bytes_pending
      [e25ba8cbfd16] iomap: Convert iomap_write_end types
      [81ee8e52a71c] iomap: Change calling convention for zeroing
      [4595a298d556] iomap: Set all uptodate bits for an Uptodate page

Nikolay Borisov (1):
      [6cc19c5fad09] iomap: Use round_down/round_up macros in __iomap_write_begin

Qian Cai (1):
      [a805c111650c] iomap: fix WARN_ON_ONCE() from unprivileged users


Code Diffstat:

 fs/dax.c                |  13 ++--
 fs/iomap/buffered-io.c  | 194 ++++++++++++++++++++----------------------------
 fs/iomap/direct-io.c    |  49 +++++++++---
 fs/jfs/jfs_metapage.c   |   2 +-
 fs/xfs/xfs_aops.c       |   2 +-
 include/linux/dax.h     |   3 +-
 include/linux/iomap.h   |   5 ++
 include/linux/pagemap.h |  16 ++++
 8 files changed, 150 insertions(+), 134 deletions(-)

                 reply	other threads:[~2020-09-28 16:13 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=20200928161117.GA49524@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=rgoldwyn@suse.de \
    --cc=willy@infradead.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).