From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: fixes for 5.5-rc1
Date: Fri, 6 Dec 2019 11:51:42 -0800 [thread overview]
Message-ID: <20191206195142.GA9464@magnolia> (raw)
Hi Linus,
Please pull these bug fixes for 5.5-rc1, which fix a couple of resource
management errors and a hang.
The branch has survived a couple of days of xfstests runs and merges
cleanly with this morning's master. Please let me know if anything
strange happens.
--D
The following changes since commit 8feb4732ff9f2732354b44c4418569974e2f949c:
xfs: allow parent directory scans to be interrupted with fatal signals (2019-11-27 08:23:14 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.5-merge-17
for you to fetch changes up to 798a9cada4694ca8d970259f216cec47e675bfd5:
xfs: fix mount failure crash on invalid iclog memory access (2019-12-03 14:53:07 -0800)
----------------------------------------------------------------
Fixes for 5.5-rc1:
- Fix a crash in the log setup code when log mounting fails
- Fix a hang when allocating space on the realtime device
- Fix a block leak when freeing space on the realtime device
----------------------------------------------------------------
Brian Foster (1):
xfs: fix mount failure crash on invalid iclog memory access
Omar Sandoval (2):
xfs: fix realtime file data space leak
xfs: don't check for AG deadlock for realtime files in bunmapi
fs/xfs/libxfs/xfs_bmap.c | 27 +++++++++++++++------------
fs/xfs/xfs_log.c | 2 ++
2 files changed, 17 insertions(+), 12 deletions(-)
next reply other threads:[~2019-12-06 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 19:51 Darrick J. Wong [this message]
2019-12-08 1:10 ` [GIT PULL] xfs: fixes for 5.5-rc1 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=20191206195142.GA9464@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.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).