From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 1/2][v2] btrfs: convert block group refcount to refcount_t
Date: Thu, 9 Jul 2020 17:39:08 +0200 [thread overview]
Message-ID: <20200709153908.GB3533@twin.jikos.cz> (raw)
In-Reply-To: <20200706131412.28870-1-josef@toxicpanda.com>
On Mon, Jul 06, 2020 at 09:14:11AM -0400, Josef Bacik wrote:
> We have refcount_t now with the associated library to handle refcounts,
> which gives us extra debugging around reference count mistakes that may
> be made. For example it'll warn on any transition from 0->1 or 0->-1,
> which is handy for noticing cases where we've messed up reference
> counting. Convert the block group ref counting from an atomic_t to
> refcount_t and use the appropriate helpers.
>
> Reviewed-by: Filipe Manana <fdmanana@suse.com>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
1 and 2 added to msic-next, thanks.
prev parent reply other threads:[~2020-07-09 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 13:14 [PATCH 1/2][v2] btrfs: convert block group refcount to refcount_t Josef Bacik
2020-07-06 13:14 ` [PATCH 2/2] btrfs: fix block group UAF bug with nocow Josef Bacik
2020-07-09 15:39 ` 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=20200709153908.GB3533@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@suse.com \
--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