From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.9-rc5
Date: Sat, 12 Sep 2020 19:01:18 +0200 [thread overview]
Message-ID: <cover.1599836573.git.dsterba@suse.com> (raw)
Hi,
a few more fixes:
- regression fix, crash after failed snapshot creation
- one more lockep fix, use nofs allocation when allocating missing
device
- fix reloc tree leak on degraded mount
- make some extent buffer alignment checks less strict to mount
filesystems created by btrfs-convert
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit f96d6960abbc52e26ad124e69e6815283d3e1674:
btrfs: tree-checker: fix the error message for transid error (2020-08-27 14:16:05 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.9-rc4-tag
for you to fetch changes up to 2d892ccdc163a3d2e08c5ed1cea8b61bf7e4f531:
btrfs: fix NULL pointer dereference after failure to create snapshot (2020-09-07 21:18:35 +0200)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: fix NULL pointer dereference after failure to create snapshot
Josef Bacik (2):
btrfs: fix lockdep splat in add_missing_dev
btrfs: free data reloc tree on failed mount
Qu Wenruo (1):
btrfs: require only sector size alignment for parent eb bytenr
fs/btrfs/disk-io.c | 2 ++
fs/btrfs/extent-tree.c | 19 +++++++++----------
fs/btrfs/print-tree.c | 12 +++++++-----
fs/btrfs/transaction.c | 1 +
fs/btrfs/volumes.c | 10 ++++++++++
5 files changed, 29 insertions(+), 15 deletions(-)
next reply other threads:[~2020-09-12 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 17:01 David Sterba [this message]
2020-09-12 20:00 ` [GIT PULL] Btrfs fixes for 5.9-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.1599836573.git.dsterba@suse.com \
--to=dsterba@suse.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 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.