From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v3 0/2] ->total_bytes_pinned fixes for early ENOSPC issues
Date: Sun, 24 Jan 2021 13:58:05 +0100 [thread overview]
Message-ID: <20210124125805.GG1993@twin.jikos.cz> (raw)
In-Reply-To: <cover.1610747242.git.josef@toxicpanda.com>
On Fri, Jan 15, 2021 at 04:48:54PM -0500, Josef Bacik wrote:
> v2->v3:
> - Updated the changelog in patch 2 to refer to the patchset that inspired the
> change.
> - Added Nik's reviewed-by for patch 2.
Thanks, the patches have been in for-next, adding v3 to misc-next.
I've tagged it for stable 5.10, though it looks like it would apply to
at least 5.4. There's a minor conflict with the way how the pinned
extents get tracked, changed in 5.7. The patchset switching to
per-transaction is not easily backportable to stable though it does not
seem to be a functionality conflict.
prev parent reply other threads:[~2021-01-24 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 21:48 [PATCH v3 0/2] ->total_bytes_pinned fixes for early ENOSPC issues Josef Bacik
2021-01-15 21:48 ` [PATCH v3 1/2] btrfs: handle ->total_bytes_pinned inside the delayed ref itself Josef Bacik
2021-01-15 21:48 ` [PATCH v3 2/2] btrfs: account for new extents being deleted in total_bytes_pinned Josef Bacik
2021-01-24 12:58 ` David Sterba [this message]
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=20210124125805.GG1993@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.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