From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: torvalds@linux-foundation.org
Cc: Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: fixes for v5.0-rc6
Date: Thu, 7 Feb 2019 23:25:17 -0800 [thread overview]
Message-ID: <20190208072517.GL7991@magnolia> (raw)
Hi Linus,
Here are a handful of XFS fixes to fix a data corruption problem, a
crasher bug, and a deadlock. It merged cleanly against this morning's
master, so please let me know if you encounter any problems.
--D
The following changes since commit 8834f5600cf3c8db365e18a3d5cac2c2780c81e5:
Linux 5.0-rc5 (2019-02-03 13:48:04 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.0-fixes-1
for you to fetch changes up to add46b3b021263c02d5a7080c58e5b459479fafd:
xfs: set buffer ops when repair probes for btree type (2019-02-03 14:03:59 -0800)
----------------------------------------------------------------
Changes since last update:
- Fix cache coherency problem with writeback mappings
- Fix buffer deadlock when shutting fs down
- Fix a null pointer dereference when running online repair
----------------------------------------------------------------
Brian Foster (2):
xfs: eof trim writeback mapping as soon as it is cached
xfs: end sync buffer I/O properly on shutdown error
Darrick J. Wong (1):
xfs: set buffer ops when repair probes for btree type
fs/xfs/scrub/repair.c | 11 ++++++++---
fs/xfs/xfs_aops.c | 2 ++
fs/xfs/xfs_buf.c | 19 +++++++++++++++++--
3 files changed, 27 insertions(+), 5 deletions(-)
next reply other threads:[~2019-02-08 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 7:25 Darrick J. Wong [this message]
2019-02-08 19:45 ` [GIT PULL] xfs: fixes for v5.0-rc6 pr-tracker-bot
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=20190208072517.GL7991@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--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).