Linux Btrfs filesystem development
 help / color / mirror / Atom feed
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 fix for 5.13-rc7
Date: Sat, 19 Jun 2021 00:03:55 +0200	[thread overview]
Message-ID: <cover.1624051838.git.dsterba@suse.com> (raw)

Hi,

one more fix, for a space accounting bug in zoned mode. It happens when
a block group is switched back rw->ro and unusable bytes (due to
zoned constraints) are subtracted twice.

It has user visible effects so I consider it important enough for late
-rc inclusion and backport to stable.

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit aefd7f7065567a4666f42c0fc8cdb379d2e036bf:

  btrfs: promote debugging asserts to full-fledged checks in validate_super (2021-06-04 13:12:06 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.13-rc6-tag

for you to fetch changes up to f9f28e5bd0baee9708c9011897196f06ae3a2733:

  btrfs: zoned: fix negative space_info->bytes_readonly (2021-06-17 11:12:14 +0200)

----------------------------------------------------------------
Naohiro Aota (1):
      btrfs: zoned: fix negative space_info->bytes_readonly

 fs/btrfs/block-group.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

             reply	other threads:[~2021-06-18 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 22:03 David Sterba [this message]
2021-06-18 23:41 ` [GIT PULL] Btrfs fix for 5.13-rc7 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.1624051838.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