From: Omar Sandoval <osandov@osandov.com>
To: linux-xfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH 0/2] xfs: fixes for realtime file truncation
Date: Tue, 26 Nov 2019 12:13:27 -0800 [thread overview]
Message-ID: <cover.1574799066.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hello,
These two patches fix bugs in a corner case of truncating realtime
files. We encountered this as a soft lockup in production while
truncating certain files, but I found the space leak on further
investigation. The lockup is caused by an interaction between the two
bugs fixed by these patches. I've also sent a reproducer for xfstests.
These patches are based on v5.4. Thanks!
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 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)
--
2.24.0
next reply other threads:[~2019-11-26 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 20:13 Omar Sandoval [this message]
2019-11-26 20:13 ` [PATCH 1/2] xfs: fix realtime file data space leak Omar Sandoval
2019-12-03 1:56 ` Darrick J. Wong
2019-11-26 20:13 ` [PATCH 2/2] xfs: don't check for AG deadlock for realtime files in bunmapi Omar Sandoval
2019-11-27 0:36 ` 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=cover.1574799066.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-xfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.