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.13-rc6
Date: Wed, 9 Jun 2021 15:28:28 +0200 [thread overview]
Message-ID: <cover.1623242687.git.dsterba@suse.com> (raw)
Hi,
a few more fixes that people hit during testing. Please pull, thanks.
- in zomed mode, fix 32bit value wrapping when calculating superblock
offsets
- error handling
- properly check filesystema and device uuids
- properly return errors when marking extents as written
- do not write supers if we have an fs error
----------------------------------------------------------------
The following changes since commit 503d1acb01826b42e5afb496dfcc32751bec9478:
MAINTAINERS: add btrfs IRC link (2021-06-03 15:40:38 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.13-rc5-tag
for you to fetch changes up to aefd7f7065567a4666f42c0fc8cdb379d2e036bf:
btrfs: promote debugging asserts to full-fledged checks in validate_super (2021-06-04 13:12:06 +0200)
----------------------------------------------------------------
Josef Bacik (1):
btrfs: do not write supers if we have an fs error
Naohiro Aota (1):
btrfs: zoned: fix zone number to sector/physical calculation
Nikolay Borisov (1):
btrfs: promote debugging asserts to full-fledged checks in validate_super
Ritesh Harjani (1):
btrfs: return value from btrfs_mark_extent_written() in case of error
fs/btrfs/disk-io.c | 26 ++++++++++++++++++--------
fs/btrfs/file.c | 4 ++--
fs/btrfs/tree-log.c | 16 ++++++++++++++++
fs/btrfs/zoned.c | 23 ++++++++++++++++++-----
4 files changed, 54 insertions(+), 15 deletions(-)
next reply other threads:[~2021-06-09 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 13:28 David Sterba [this message]
2021-06-09 21:59 ` [GIT PULL] Btrfs fixes for 5.13-rc6 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.1623242687.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).