linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next branch updated to 5f1c6d28cfcd
Date: Wed, 30 Nov 2016 16:04:30 +1100	[thread overview]
Message-ID: <20161130050430.GG31101@dastard> (raw)

Hi folks,

The for-next branch of the xfs kernel repository at

git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git

has just been updated. This is a merge of the new iomap-based direct
IO code, and the conversion of XFS to use it. It also removes the
XFs inode i_iolock and replaces it with the vfs inode i_rwsem, so
simplifying the locking heirarchy used within XFS.

-Dave.

The new head of the for-next branch is commit:

5f1c6d28cfcd Merge branch 'iomap-4.10-directio' into for-next

New Commits:

Christoph Hellwig (4):
      [6552321831dc] xfs: remove i_iolock and use i_rwsem in the VFS inode instead
      [ec1b826097f3] fs: make sb_init_dio_done_wq available outside of direct-io.c
      [ff6a9292e6f6] iomap: implement direct I/O
      [acdda3aae146] xfs: use iomap_dio_rw

Dave Chinner (2):
      [e3df41f97847] Merge branch 'xfs-4.10-misc-fixes-2' into iomap-4.10-directio
      [5f1c6d28cfcd] Merge branch 'iomap-4.10-directio' into for-next

Kent Overstreet (1):
      [3816199506c7] block: add bio_iov_iter_get_pages()

Peter Zijlstra (1):
      [f8319483f57f] locking/lockdep: Provide a type check for lock_is_held


Code Diffstat:

 block/bio.c               |  49 ++++++
 fs/direct-io.c            |   2 +-
 fs/internal.h             |   3 +
 fs/iomap.c                | 373 ++++++++++++++++++++++++++++++++++++++++++++++
 fs/xfs/xfs_aops.c         | 298 ++----------------------------------
 fs/xfs/xfs_aops.h         |   6 -
 fs/xfs/xfs_bmap_util.c    |  12 +-
 fs/xfs/xfs_dir2_readdir.c |   2 -
 fs/xfs/xfs_file.c         | 226 ++++++++++------------------
 fs/xfs/xfs_icache.c       |   6 +-
 fs/xfs/xfs_inode.c        |  82 ++++------
 fs/xfs/xfs_inode.h        |   7 +-
 fs/xfs/xfs_ioctl.c        |   2 +-
 fs/xfs/xfs_iomap.c        |  50 ++++++-
 fs/xfs/xfs_iops.c         |  14 +-
 fs/xfs/xfs_pnfs.c         |   7 +-
 fs/xfs/xfs_pnfs.h         |   4 +-
 fs/xfs/xfs_reflink.c      |  14 +-
 fs/xfs/xfs_super.c        |   2 +-
 fs/xfs/xfs_symlink.c      |   7 +-
 include/linux/bio.h       |   1 +
 include/linux/iomap.h     |  11 ++
 include/linux/lockdep.h   |  25 +++-
 kernel/locking/lockdep.c  |  20 ++-
 24 files changed, 668 insertions(+), 555 deletions(-)
-- 
Dave Chinner
david@fromorbit.com

                 reply	other threads:[~2016-11-30  5:04 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=20161130050430.GG31101@dastard \
    --to=david@fromorbit.com \
    --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;
as well as URLs for NNTP newsgroup(s).