From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
clm@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.0-rc5
Date: Sun, 3 Feb 2019 10:48:46 +0100 [thread overview]
Message-ID: <cover.1549186243.git.dsterba@suse.com> (raw)
Hi,
there are a few fixes that I'd like to have in the 5.0 release. Last rc
was skipped because one fix had to be reworked and more testing was
needed. Please pull, thanks.
- regression fix: transaction commit can run away due to delayed ref
waiting heuristic, this is not necessary now because of the proper
reservation mechanism introduced in 5.0
- regression fix: potential crash due to use-before-check of an ERR_PTR
return value
- fix for transaction abort during transaction commit that needs to
properly clean up pending block groups
- fix deadlock during b-tree node/leaf splitting, when this happens on
some of the fundamental trees, we must prevent new tree block
allocation to re-enter indirectly via the block group flushing path
- potential memory leak after errors during mount
----------------------------------------------------------------
The following changes since commit fd340d0f68cc87badfc9efcb226f23a5428826a0:
btrfs: wakeup cleaner thread when adding delayed iput (2019-01-18 17:27:23 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.0-rc4-tag
for you to fetch changes up to 532b618bdf237250d6d4566536d4b6ce3d0a31fe:
btrfs: On error always free subvol_name in btrfs_mount (2019-01-30 18:16:47 +0100)
----------------------------------------------------------------
Al Viro (1):
btrfs: fix potential oops in device_list_add
David Sterba (1):
btrfs: clean up pending block groups when transaction commit aborts
Eric W. Biederman (1):
btrfs: On error always free subvol_name in btrfs_mount
Filipe Manana (1):
Btrfs: fix deadlock when allocating tree block during leaf/node split
Josef Bacik (1):
btrfs: don't end the transaction for delayed refs in throttle
fs/btrfs/ctree.c | 78 ++++++++++++++++++++++++++++++++------------------
fs/btrfs/super.c | 3 ++
fs/btrfs/transaction.c | 24 ++++++++++------
fs/btrfs/volumes.c | 4 +--
4 files changed, 71 insertions(+), 38 deletions(-)
next reply other threads:[~2019-02-03 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 9:48 David Sterba [this message]
2019-02-03 17:50 ` [GIT PULL] Btrfs fixes for 5.0-rc5 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=cover.1549186243.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).