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>,
agruenba@redhat.com, Christoph Hellwig <hch@infradead.org>
Subject: [GIT PULL] xfs: 4.19 merge, part 3
Date: Tue, 21 Aug 2018 08:12:44 -0700 [thread overview]
Message-ID: <20180821151244.GC4334@magnolia> (raw)
Hi Linus,
Here are a few fixes that I've queued up for 4.19. I need to recover
from some medical events, so don't be too surprised if the next pull
request(s) come from Dave Chinner.
--D
The following changes since commit 01239d77b9dd978863d1a75f0d095ab942a1fe66:
xfs: fix a null pointer dereference in xfs_bmap_extents_to_btree (2018-08-12 08:37:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.19-merge-7
for you to fetch changes up to 7d5e049e72c4cb933b557c78cbd63285dd8102ce:
iomap: fix WARN_ON_ONCE on uninitialized variable (2018-08-14 08:17:02 -0700)
----------------------------------------------------------------
Changes since last update:
- Fix an uninitialized variable
- Don't use obviously garbage AG header counters to calculate
transaction reservations
- Trigger icount recalculation on bad icount when monting.
----------------------------------------------------------------
Darrick J. Wong (3):
xfs: recalculate summary counters at mount time if icount is bad
xfs: sanity check ag header values in xrep_calc_ag_resblks
iomap: fix WARN_ON_ONCE on uninitialized variable
fs/iomap.c | 2 +-
fs/xfs/scrub/repair.c | 46 +++++++++++++++++++++++++++-------------------
fs/xfs/xfs_mount.c | 1 +
3 files changed, 29 insertions(+), 20 deletions(-)
reply other threads:[~2018-08-21 18:33 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=20180821151244.GC4334@magnolia \
--to=djwong@kernel.org \
--cc=agruenba@redhat.com \
--cc=hch@infradead.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).