From: "Darrick J. Wong" <djwong@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.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 2
Date: Thu, 26 Jul 2018 11:22:43 -0700 [thread overview]
Message-ID: <20180726182243.GG30972@magnolia> (raw)
In-Reply-To: <20180627182421.GE5711@magnolia>
Hi Linus,
Here are a couple of late patches for 4.18 to fix a coding bug
introduced in -rc1 and a fix for incorrect metadata verification of
on-disk data.
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 d8cb5e42378918e00eda58792f3ab86dd1e7d214:
xfs: fix fdblocks accounting w/ RMAPBT per-AG reservation (2018-06-24 12:00:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.18-fixes-4
for you to fetch changes up to d4a34e16555708bab5b67e679a95f055d8ef9882:
xfs: properly handle free inodes in extent hint validators (2018-07-24 11:34:52 -0700)
----------------------------------------------------------------
Changes since last update:
- Fix some uninitialized variable errors
- Fix an incorrect check in metadata verifiers
----------------------------------------------------------------
Carlos Maiolino (1):
xfs: Initialize variables in xfs_alloc_get_rec before using them
Eric Sandeen (1):
xfs: properly handle free inodes in extent hint validators
fs/xfs/libxfs/xfs_alloc.c | 5 +++--
fs/xfs/libxfs/xfs_inode_buf.c | 6 ++++--
2 files changed, 7 insertions(+), 4 deletions(-)
prev parent reply other threads:[~2018-07-26 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 18:24 [GIT PULL] xfs: 4.18 fixes, part 1 Darrick J. Wong
2018-07-26 18:22 ` Darrick J. Wong [this message]
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=20180726182243.GG30972@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).