From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>
Subject: [GIT PULL] xfs: 4.18 fixes, part 1
Date: Wed, 27 Jun 2018 11:24:21 -0700 [thread overview]
Message-ID: <20180627182421.GE5711@magnolia> (raw)
Hi Linus,
Here are some patches for 4.18 to fix regressions, accounting problems,
overflow problems, and to strengthen metadata validation to prevent
corruption.
This series has been run through a full xfstests run over the weekend
and through a quick xfstests run against this morning's master, with no
major failures reported.
--D
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.18-fixes-2
for you to fetch changes up to d8cb5e42378918e00eda58792f3ab86dd1e7d214:
xfs: fix fdblocks accounting w/ RMAPBT per-AG reservation (2018-06-24 12:00:12 -0700)
----------------------------------------------------------------
Changes since last update:
- More metadata validation strengthening to prevent crashes.
- Fix extent offset overflow problem when insert_range on a 512b block fs
- Fix some off-by-one errors in the realtime fsmap code
- Fix some math errors in the default resblks calculation when free space
is low
- Fix a problem where stale page contents are exposed via mmap read
after a zero_range at eof
- Fix accounting problems with per-ag reservations causing statfs
reports to vary incorrectly
----------------------------------------------------------------
Christoph Hellwig (1):
xfs: simplify xfs_bmap_punch_delalloc_range
Darrick J. Wong (8):
xfs: allow empty transactions while frozen
xfs: don't trip over negative free space in xfs_reserve_blocks
xfs: don't allow insert-range to shift extents past the maximum offset
xfs: recheck reflink state after grabbing ILOCK_SHARED for a write
xfs: fix uninitialized field in rtbitmap fsmap backend
xfs: fix off-by-one error in xfs_rtalloc_query_range
xfs: ensure post-EOF zeroing happens after zeroing part of a file
xfs: fix fdblocks accounting w/ RMAPBT per-AG reservation
Dave Chinner (2):
xfs: More robust inode extent count validation
xfs: xfs_iflush_abort() can be called twice on cluster writeback failure
fs/xfs/libxfs/xfs_ag_resv.c | 31 ++++++++++--
fs/xfs/libxfs/xfs_bmap.c | 26 +++++++++++
fs/xfs/libxfs/xfs_bmap.h | 2 +
fs/xfs/libxfs/xfs_format.h | 5 ++
fs/xfs/libxfs/xfs_inode_buf.c | 76 ++++++++++++++++++------------
fs/xfs/libxfs/xfs_rtbitmap.c | 4 +-
fs/xfs/xfs_bmap_util.c | 106 +++++++++++++++++++++---------------------
fs/xfs/xfs_fsmap.c | 4 +-
fs/xfs/xfs_fsops.c | 2 +-
fs/xfs/xfs_inode.c | 57 +++++++++--------------
fs/xfs/xfs_iomap.c | 15 +++++-
fs/xfs/xfs_trans.c | 7 ++-
12 files changed, 205 insertions(+), 130 deletions(-)
next reply other threads:[~2018-06-27 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 18:24 Darrick J. Wong [this message]
2018-07-26 18:22 ` [GIT PULL] xfs: 4.18 fixes, part 2 Darrick J. Wong
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=20180627182421.GE5711@magnolia \
--to=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.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).