From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch rebased and updated to 264e89a
Date: Tue, 3 Nov 2015 16:06:52 +1100 [thread overview]
Message-ID: <20151103050652.GC19199@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2782 bytes --]
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. I rebased the xfs-misc-fixes-for-4.4-2 branch
to fix the ACL build issue and added Andreas' and Darrick's bug
fixes, and so the for-next branch has rebased as well. This update
also includes all the DAX fixes queued up for 4.4.
-Dave.
The new head of the for-next branch is commit:
264e89a Merge branch 'xfs-dax-updates' into for-next
New Commits:
Andreas Gruenbacher (3):
[86a21c7] xfs: Validate the length of on-disk ACLs
[09cb22d] xfs: Plug memory leak in xfs_attrmulti_attr_set
[47e1bf6] xfs: invalidate cached acl if set via ioctl
Brian Foster (1):
[67d8e04] xfs: invalidate cached acl if set directly via xattr
Darrick J. Wong (1):
[af3b638] xfs: don't leak uuid table on rmmod
Dave Chinner (9):
[3e12dbb] xfs: fix inode size update overflow in xfs_map_direct()
[3fbbbea] xfs: introduce BMAPI_ZERO for allocating zeroed extents
[1ca1915] xfs: Don't use unwritten extents for DAX
[01a155e] xfs: DAX does not use IO completion callbacks
[3af4928] xfs: add ->pfn_mkwrite support for DAX
[13ad4fe] xfs: xfs_filemap_pmd_fault treats read faults as write faults
[fc0561c] xfs: optimise away log forces on timestamp updates for fdatasync
[2da5c4b] Merge branch 'xfs-misc-fixes-for-4.4-2' into for-next
[264e89a] Merge branch 'xfs-dax-updates' into for-next
Jiri Kosina (1):
[24ba16b] xfs: clear PF_NOFREEZE for xfsaild kthread
Code Diffstat:
fs/dax.c | 5 +++
fs/xfs/libxfs/xfs_alloc.c | 10 ++++-
fs/xfs/libxfs/xfs_alloc.h | 8 ++--
fs/xfs/libxfs/xfs_bmap.c | 35 ++++++++++++++++-
fs/xfs/libxfs/xfs_bmap.h | 13 ++++++-
fs/xfs/libxfs/xfs_format.h | 8 +++-
fs/xfs/xfs_acl.c | 13 ++++---
fs/xfs/xfs_acl.h | 3 ++
fs/xfs/xfs_aops.c | 96 ++++++++++++++++++++++++----------------------
fs/xfs/xfs_aops.h | 3 +-
fs/xfs/xfs_bmap_util.c | 36 +++++++++++++++++
fs/xfs/xfs_file.c | 85 +++++++++++++++++++++++++++++++++-------
fs/xfs/xfs_inode.c | 2 +
fs/xfs/xfs_inode_item.c | 1 +
fs/xfs/xfs_inode_item.h | 1 +
fs/xfs/xfs_ioctl.c | 15 +++++++-
fs/xfs/xfs_iomap.c | 21 +++++++++-
fs/xfs/xfs_mount.c | 10 +++++
fs/xfs/xfs_mount.h | 4 ++
fs/xfs/xfs_super.c | 1 +
fs/xfs/xfs_trace.h | 1 +
fs/xfs/xfs_trans_ail.c | 1 +
fs/xfs/xfs_trans_inode.c | 9 +++++
fs/xfs/xfs_xattr.c | 31 ++++++++++++++-
24 files changed, 331 insertions(+), 81 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2015-11-03 5:07 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=20151103050652.GC19199@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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