From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com, Filipe Manana <fdmanana@suse.com>
Subject: [GIT PULL] Btrfs fixes
Date: Thu, 5 Nov 2015 11:20:37 +0000 [thread overview]
Message-ID: <1446722437-21605-1-git-send-email-fdmanana@kernel.org> (raw)
From: Filipe Manana <fdmanana@suse.com>
Hi Chris,
please consider the following fixes for the 4.4 merge window (they were
all previously sent to the mailing list already).
One fixes a sleep inside atomic context issue, introduced by one patch
in the integration-4.4 branch. Another two fix races regarding waiting
for qgroup rescan worker to finish and a race between the qgroup rescan
worker and unmounting the filesystem (leading to crashes). The remaining
patch fixes an issue with partial direct IO writes, which has been
introduced in the 4.0 kernel, and results either in an assertion failure
(BUG_ON) when CONFIG_BTRFS_ASSERT=y or arithmetic underflow of an inode's
outstanding extents counter (used for proper space reservation) when
assertions are disabled.
Two test cases for fstests were sent recently to cover the issues regarding
the races and the direct IO partial write regression.
Thanks.
The following changes since commit 2959a32a858a2c44bbbce83d19c158d54cc5998a:
Btrfs: fix hole punching when using the no-holes feature (2015-11-03 07:44:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/fdmanana/linux.git integration-4.4
for you to fetch changes up to 3b2ba7b31d56c3d8f57cd5d32b8fb5101ab446e4:
Btrfs: fix sleeping inside atomic context in qgroup rescan worker (2015-11-05 11:02:22 +0000)
----------------------------------------------------------------
Filipe Manana (3):
Btrfs: fix extent accounting for partial direct IO writes
Btrfs: fix race waiting for qgroup rescan worker
Btrfs: fix sleeping inside atomic context in qgroup rescan worker
Justin Maggard (1):
btrfs: qgroup: exit the rescan worker during umount
fs/btrfs/disk-io.c | 3 +++
fs/btrfs/inode.c | 52 +++++++++++++++++++++++++++++++++++++---------------
fs/btrfs/qgroup.c | 13 +++++++------
3 files changed, 47 insertions(+), 21 deletions(-)
--
2.1.3
next reply other threads:[~2015-11-05 11:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 11:20 fdmanana [this message]
2015-11-05 14:59 ` [GIT PULL] Btrfs fixes Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2017-01-13 22:01 Chris Mason
2015-05-15 19:11 Chris Mason
2015-05-01 14:08 Chris Mason
2015-04-26 13:18 Chris Mason
2015-03-20 16:55 Chris Mason
2015-01-23 18:49 Chris Mason
2015-01-08 18:28 Chris Mason
2014-11-01 16:05 Chris Mason
2014-09-19 19:47 Chris Mason
2013-03-17 12:34 Chris Mason
2013-02-07 0:13 Chris Mason
2013-02-07 0:09 Chris Mason
2013-01-23 0:48 Chris Mason
2013-01-23 1:28 ` Liu Bo
2013-01-23 1:40 ` Chris Mason
2013-01-24 21:52 ` Chris Mason
2013-01-25 3:13 ` Linus Torvalds
2012-10-26 14:19 Chris Mason
2012-05-06 13:35 Chris Mason
2012-04-28 12:27 Chris Mason
2012-01-27 16:34 Chris Mason
2012-01-27 16:31 Chris Mason
2011-12-23 17:24 Chris Mason
2011-12-16 17:53 Chris Mason
2011-12-16 18:20 ` Chris Mason
2011-12-16 18:29 ` nobody
2011-12-08 19:24 Chris Mason
2011-11-22 1:30 Chris Mason
2011-11-11 21:40 Chris Mason
2011-09-19 23:57 Chris Mason
2011-09-20 16:19 ` Sage Weil
2011-07-08 18:55 [GIT PULL] btrfs fixes Chris Mason
2011-07-11 11:31 ` Tarkan Erimer
2010-04-12 20:00 [GIT PULL] Btrfs fixes Chris Mason
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=1446722437-21605-1-git-send-email-fdmanana@kernel.org \
--to=fdmanana@kernel.org \
--cc=clm@fb.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@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 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).