[ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d

[ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d

[Darrick J. Wong]

Hi folks,

The for-next 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.

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

1baa2800e62d xfs: remove the unused XFS_ALLOC_USERDATA flag

New Commits:

Christoph Hellwig (3):
      [adcb0ca2330b] xfs: fix the dax supported check in xfs_ioctl_setattr_dax_invalidate
      [ecfc28a41cf1] xfs: cleanup xfs_fsb_to_db
      [1baa2800e62d] xfs: remove the unused XFS_ALLOC_USERDATA flag

Darrick J. Wong (11):
      [519e5869d50d] xfs: bmap scrub should only scrub records once
      [c94613feefd7] xfs: fix maxicount division by zero error
      [7380e8fec16b] xfs: don't return _QUERY_ABORT from xfs_rmap_has_other_keys
      [b521c89027f4] xfs: fix sign handling problem in xfs_bmbt_diff_two_keys
      [2ca09177ab9d] xfs: remove unnecessary parameter from xfs_iext_inc_seq
      [bc46ac64713f] xfs: remove unnecessary int returns from deferred rmap functions
      [74b4c5d4a9c0] xfs: remove unnecessary int returns from deferred refcount functions
      [3e08f42ae782] xfs: remove unnecessary int returns from deferred bmap functions
      [ffb5696f7555] xfs: reinitialize rm_flags when unpacking an offset into an rmap irec
      [e7ee96dfb8c2] xfs: remove all *_ITER_ABORT values
      [39ee2239a5a2] xfs: remove all *_ITER_CONTINUE values

Dave Chinner (13):
      [0ad95687c3ad] xfs: add kmem allocation trace points
      [d916275aa4dd] xfs: get allocation alignment from the buftarg
      [f8f9ee479439] xfs: add kmem_alloc_io()
      [aee7754bbeb1] xfs: move xfs_dir2_addname()
      [a07258a69528] xfs: factor data block addition from xfs_dir2_node_addname_int()
      [0e822255f95d] xfs: factor free block index lookup from xfs_dir2_node_addname_int()
      [610125ab1e4b] xfs: speed up directory bestfree block scanning
      [756c6f0f7efe] xfs: reverse search directory freespace indexes
      [728bcaa3e0f9] xfs: make attr lookup returns consistent
      [a0e959d3c9d5] xfs: remove unnecessary indenting from xfs_attr3_leaf_getvalue
      [e3cc4554ce1b] xfs: move remote attr retrieval into xfs_attr3_leaf_getvalue
      [9df243a1a9e6] xfs: consolidate attribute value copying
      [ddbca70cc45c] xfs: allocate xattr buffer on demand

Eric Sandeen (1):
      [7f313eda8fcc] xfs: log proper length of btree block in scrub/repair

Jan Kara (3):
      [692fe62433d4] mm: Handle MADV_WILLNEED through vfs_fadvise()
      [cf1ea0592dbf] fs: Export generic_fadvise()
      [40144e49ff84] xfs: Fix stale data exposure when readahead races with hole punch

Tetsuo Handa (1):
      [707e0ddaf67e] fs: xfs: Remove KM_NOSLEEP and KM_SLEEP.

zhengbin (1):
      [71912e08e06b] xfs: remove excess function parameter description in 'xfs_btree_sblock_v5hdr_verify'


Code Diffstat:

 fs/xfs/kmem.c                   |  79 +++--
 fs/xfs/kmem.h                   |  15 +-
 fs/xfs/libxfs/xfs_alloc.c       |   2 +-
 fs/xfs/libxfs/xfs_alloc.h       |   7 +-
 fs/xfs/libxfs/xfs_attr.c        |  79 +++--
 fs/xfs/libxfs/xfs_attr.h        |   6 +-
 fs/xfs/libxfs/xfs_attr_leaf.c   | 130 ++++----
 fs/xfs/libxfs/xfs_attr_remote.c |   2 +
 fs/xfs/libxfs/xfs_bmap.c        |  83 ++---
 fs/xfs/libxfs/xfs_bmap.h        |   4 +-
 fs/xfs/libxfs/xfs_bmap_btree.c  |  16 +-
 fs/xfs/libxfs/xfs_btree.c       |  14 +-
 fs/xfs/libxfs/xfs_btree.h       |  10 +-
 fs/xfs/libxfs/xfs_da_btree.c    |   6 +-
 fs/xfs/libxfs/xfs_da_btree.h    |   4 +-
 fs/xfs/libxfs/xfs_defer.c       |   2 +-
 fs/xfs/libxfs/xfs_dir2.c        |  14 +-
 fs/xfs/libxfs/xfs_dir2_block.c  |   2 +-
 fs/xfs/libxfs/xfs_dir2_node.c   | 678 +++++++++++++++++++---------------------
 fs/xfs/libxfs/xfs_dir2_sf.c     |   8 +-
 fs/xfs/libxfs/xfs_ialloc.c      |   9 +-
 fs/xfs/libxfs/xfs_iext_tree.c   |   8 +-
 fs/xfs/libxfs/xfs_inode_fork.c  |  16 +-
 fs/xfs/libxfs/xfs_refcount.c    |  50 ++-
 fs/xfs/libxfs/xfs_refcount.h    |  12 +-
 fs/xfs/libxfs/xfs_rmap.c        |  59 ++--
 fs/xfs/libxfs/xfs_rmap.h        |  11 +-
 fs/xfs/libxfs/xfs_shared.h      |   6 -
 fs/xfs/libxfs/xfs_types.h       |   8 +
 fs/xfs/scrub/agheader.c         |   4 +-
 fs/xfs/scrub/attr.c             |   6 +-
 fs/xfs/scrub/bmap.c             |  81 +++--
 fs/xfs/scrub/fscounters.c       |   2 +-
 fs/xfs/scrub/repair.c           |   6 +-
 fs/xfs/scrub/symlink.c          |   2 +-
 fs/xfs/xfs_acl.c                |  14 +-
 fs/xfs/xfs_attr_inactive.c      |   2 +-
 fs/xfs/xfs_attr_list.c          |   2 +-
 fs/xfs/xfs_bmap_item.c          |   8 +-
 fs/xfs/xfs_bmap_util.c          |  22 +-
 fs/xfs/xfs_buf.c                |   7 +-
 fs/xfs/xfs_buf.h                |   6 +
 fs/xfs/xfs_buf_item.c           |   4 +-
 fs/xfs/xfs_dquot.c              |   4 +-
 fs/xfs/xfs_dquot_item.c         |   2 +-
 fs/xfs/xfs_error.c              |   2 +-
 fs/xfs/xfs_extent_busy.c        |   2 +-
 fs/xfs/xfs_extfree_item.c       |   8 +-
 fs/xfs/xfs_file.c               |  26 ++
 fs/xfs/xfs_fsmap.c              |  12 +-
 fs/xfs/xfs_icache.c             |   2 +-
 fs/xfs/xfs_icreate_item.c       |   2 +-
 fs/xfs/xfs_inode.c              |   2 +-
 fs/xfs/xfs_inode_item.c         |   2 +-
 fs/xfs/xfs_ioctl.c              |  21 +-
 fs/xfs/xfs_ioctl32.c            |   2 +-
 fs/xfs/xfs_itable.c             |  10 +-
 fs/xfs/xfs_itable.h             |  13 +-
 fs/xfs/xfs_iwalk.c              |   4 +-
 fs/xfs/xfs_iwalk.h              |  13 +-
 fs/xfs/xfs_log.c                |   8 +-
 fs/xfs/xfs_log_cil.c            |  10 +-
 fs/xfs/xfs_log_recover.c        |  20 +-
 fs/xfs/xfs_mount.c              |   2 +-
 fs/xfs/xfs_mount.h              |   7 -
 fs/xfs/xfs_mru_cache.c          |   4 +-
 fs/xfs/xfs_qm.c                 |   4 +-
 fs/xfs/xfs_refcount_item.c      |  16 +-
 fs/xfs/xfs_reflink.c            |  23 +-
 fs/xfs/xfs_rmap_item.c          |   6 +-
 fs/xfs/xfs_rtalloc.c            |   4 +-
 fs/xfs/xfs_trace.h              |  34 ++
 fs/xfs/xfs_trans.c              |   4 +-
 fs/xfs/xfs_trans_dquot.c        |   2 +-
 fs/xfs/xfs_xattr.c              |   2 +-
 include/linux/fs.h              |   2 +
 mm/fadvise.c                    |   4 +-
 mm/madvise.c                    |  22 +-
 78 files changed, 961 insertions(+), 846 deletions(-)

Re: [ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d

[Christoph Hellwig]

On Sat, Aug 31, 2019 at 12:39:17PM -0700, Darrick J. Wong wrote:
> Dave Chinner (13):
>       [0ad95687c3ad] xfs: add kmem allocation trace points
>       [d916275aa4dd] xfs: get allocation alignment from the buftarg
>       [f8f9ee479439] xfs: add kmem_alloc_io()

Btw, shouldn't these go into 5.3-rc?  Linus also mentioned to me in a
private mail that he is going to do a -rc8 due to his travel schedule,
so we'd at least have some soaking time.

Re: [ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d

[Darrick J. Wong]

On Sun, Sep 01, 2019 at 12:33:11AM -0700, Christoph Hellwig wrote:
> On Sat, Aug 31, 2019 at 12:39:17PM -0700, Darrick J. Wong wrote:
> > Dave Chinner (13):
> >       [0ad95687c3ad] xfs: add kmem allocation trace points
> >       [d916275aa4dd] xfs: get allocation alignment from the buftarg
> >       [f8f9ee479439] xfs: add kmem_alloc_io()
> 
> Btw, shouldn't these go into 5.3-rc?  Linus also mentioned to me in a
> private mail that he is going to do a -rc8 due to his travel schedule,
> so we'd at least have some soaking time.

/me shrugs -- it's been broken for years, apparently, and we've been
arguing with almost no action for months.  Developers who are building
things off of 5.3 should probably just add the patch (or turn off slub
debugging)....

--D

Re: [ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d

[Christoph Hellwig]

On Tue, Sep 03, 2019 at 04:40:24PM -0700, Darrick J. Wong wrote:
> /me shrugs -- it's been broken for years, apparently, and we've been
> arguing with almost no action for months.  Developers who are building
> things off of 5.3 should probably just add the patch (or turn off slub
> debugging)....

Well, this is a new breakage with the same old root cause.  The root
cause is that slub with debugging enabled gives us unaligned memory.

But with my log recovery changes we may now use slub for allocations
larger than a single page (before we only used it for smaller than
page sizes allocations in the buffer cache), and that newly trips
up in the pmem driver (and a few others).

> 
> --D
---end quoted text---

Re: [ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d

[Christoph Hellwig]

On Tue, Sep 03, 2019 at 10:06:27PM -0700, Christoph Hellwig wrote:
> On Tue, Sep 03, 2019 at 04:40:24PM -0700, Darrick J. Wong wrote:
> > /me shrugs -- it's been broken for years, apparently, and we've been
> > arguing with almost no action for months.  Developers who are building
> > things off of 5.3 should probably just add the patch (or turn off slub
> > debugging)....
> 
> Well, this is a new breakage with the same old root cause.  The root
> cause is that slub with debugging enabled gives us unaligned memory.
> 
> But with my log recovery changes we may now use slub for allocations
> larger than a single page (before we only used it for smaller than
> page sizes allocations in the buffer cache), and that newly trips
> up in the pmem driver (and a few others).

Another ping.  It would be really sad to release 5.3 with a known
regression we've fixed two weeks before the release.