From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to e55ec4ddbef9
Date: Mon, 1 Oct 2018 10:49:09 +1000 [thread overview]
Message-ID: <20181001004909.GG18567@dastard> (raw)
[-- Attachment #1: Type: text/plain, Size: 2727 bytes --]
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.
This update contains fixes for the 4.19-rc6 cycle, I'll be pulling
in stuff for the 4.20 merge window over the next few days.
Cheers,
Dave.
The new head of the for-next branch is commit:
e55ec4ddbef9 xfs: fix error handling in xfs_bmap_extents_to_btree
----------------------------------------------------------------
Brian Foster (6):
xfs: remove last of unnecessary xfs_defer_cancel() callers
xfs: don't unlock invalidated buf on aborted tx commit
xfs: clean up xfs_trans_brelse()
xfs: refactor xfs_buf_log_item reference count handling
xfs: remove invalid log recovery first/last cycle check
iomap: set page dirty after partial delalloc on mkwrite
Christoph Hellwig (2):
xfs: don't bring in extents in xfs_bmap_punch_delalloc_range
xfs: skip delalloc COW blocks in xfs_reflink_end_cow
Darrick J. Wong (1):
xfs: don't crash the vfs on a garbage inline symlink
Dave Chinner (3):
xfs: avoid lockdep false positives in xfs_trans_alloc
xfs: fix transaction leak in xfs_reflink_allocate_cow()
xfs: fix error handling in xfs_bmap_extents_to_btree
Eric Sandeen (2):
xfs: don't treat unknown di_flags2 as corruption in scrub
xfs: validate inode di_forkoff
YueHaibing (1):
xfs: remove duplicated include from alloc.c
fs/iomap.c | 2 +-
fs/xfs/libxfs/xfs_attr.c | 28 +++-----
fs/xfs/libxfs/xfs_attr_remote.c | 10 +--
fs/xfs/libxfs/xfs_bmap.c | 24 +++----
fs/xfs/libxfs/xfs_format.h | 2 +
fs/xfs/libxfs/xfs_inode_buf.c | 30 +++++++++
fs/xfs/scrub/alloc.c | 1 -
fs/xfs/scrub/inode.c | 4 +-
fs/xfs/xfs_bmap_util.c | 20 ++----
fs/xfs/xfs_buf_item.c | 119 ++++++++++++++++++----------------
fs/xfs/xfs_buf_item.h | 1 +
fs/xfs/xfs_inode.c | 10 +--
fs/xfs/xfs_iops.c | 12 +++-
fs/xfs/xfs_log_recover.c | 10 ---
fs/xfs/xfs_reflink.c | 137 ++++++++++++++++++++++++----------------
fs/xfs/xfs_trace.h | 1 -
fs/xfs/xfs_trans.c | 10 ++-
fs/xfs/xfs_trans_buf.c | 99 +++++++----------------------
18 files changed, 256 insertions(+), 264 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2018-10-01 7:24 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=20181001004909.GG18567@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).