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 fro 5.14-rc4
Date: Fri, 30 Jul 2021 16:40:59 +0200 [thread overview]
Message-ID: <cover.1627655635.git.dsterba@suse.com> (raw)
Hi,
a few more fixes, please pull thanks.
* fix -Warray-bounds warning, to help external patchset to make it
default treewide
* fix writeable device accounting (syzbot report)
* fix fsync and log replay after a rename and inode eviction
* fix potentially lost error code when submitting multiple bios for
compressed range
----------------------------------------------------------------
The following changes since commit c7c3a6dcb1efd52949acc1e640be9aad1206a13a:
btrfs: store a block_device in struct btrfs_ordered_extent (2021-07-22 15:50:15 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.14-rc3-tag
for you to fetch changes up to 7280305eb57dd32735f795ed4ee679bf9854f9d0:
btrfs: calculate number of eb pages properly in csum_tree_block (2021-07-29 13:01:04 +0200)
----------------------------------------------------------------
David Sterba (1):
btrfs: calculate number of eb pages properly in csum_tree_block
Desmond Cheong Zhi Xi (1):
btrfs: fix rw device counting in __btrfs_free_extra_devids
Filipe Manana (1):
btrfs: fix lost inode on log replay after mix of fsync, rename and inode eviction
Goldwyn Rodrigues (1):
btrfs: mark compressed range uptodate only if all bio succeed
fs/btrfs/compression.c | 2 +-
fs/btrfs/disk-io.c | 2 +-
fs/btrfs/tree-log.c | 4 ++--
fs/btrfs/volumes.c | 1 +
4 files changed, 5 insertions(+), 4 deletions(-)
next reply other threads:[~2021-07-30 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 14:40 David Sterba [this message]
2021-07-30 18:11 ` [GIT PULL] Btrfs fixes fro 5.14-rc4 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.1627655635.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 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).