From: Gabriel Niebler <gniebler@suse.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.com
Subject: Re: [PATCH v5] btrfs: Turn delayed_nodes_tree into an XArray
Date: Mon, 25 Apr 2022 10:49:19 +0200 [thread overview]
Message-ID: <730c253b-e595-b898-cf2d-54aa5ade8eba@suse.com> (raw)
In-Reply-To: <9a8d4a62-8ca9-9ee3-2d94-8094428dd182@suse.com>
Am 20.04.22 um 09:09 schrieb Nikolay Borisov:
> On 19.04.22 г. 18:57 ч., Gabriel Niebler wrote:
>> @@ -1870,29 +1863,33 @@ void btrfs_kill_delayed_inode_items(struct
>> btrfs_inode *inode)
>> void btrfs_kill_all_delayed_nodes(struct btrfs_root *root)
>> {
>> - u64 inode_id = 0;
>> + unsigned long index = 0;
>> + struct btrfs_delayed_node *delayed_node;
>> struct btrfs_delayed_node *delayed_nodes[8];
>
> Actually in order for the new code to be correct this array needs to be
> zero-initialized upon every iteration of the while() loop. That's
> because as it stands ATM delayed_nodes would retain the value from the
> previous iteration. What this could lead to is on the last iteration we
> potentially have 8 nodes in delayed_nodes which have been freed, so if
> in the last iteration of the xa_for_each_start we copy only 3 nodes the
> array would still have 8 nodes in total - 3 from the last iteration and
> 5 stale from the previous since they haven't been cleared out. So the
> final for() loop which does the freeing would incur a double free on the
> 5 already-freed entries.
Oh, you're right! I must not have thought about the *last* iteration,
but yeah: that's a problem!
> To fix this you either need to clear delayed_nodes[i] in the final for
> loop, so simply define it inside the while() like so:
>
> struct btrfs_delayed_node *delayed_nodes[8] = {};
I will do that. Thanks for introducing me to this neat trick how to
initialise an array to all NULLs, BTW. I admit I had to look it up, but
now it'll save me from writing another loop...
<snip>
I'll also use the opportunity to fix the whitespace issues.
Sorry for the delay, BTW, don't know why I didn't see the message earlier.
next prev parent reply other threads:[~2022-04-25 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 15:57 [PATCH v5] btrfs: Turn delayed_nodes_tree into an XArray Gabriel Niebler
2022-04-19 16:05 ` Roman Mamedov
2022-04-19 20:23 ` David Sterba
2022-04-20 7:01 ` Nikolay Borisov
2022-04-20 7:09 ` Nikolay Borisov
2022-04-25 8:49 ` Gabriel Niebler [this message]
2022-04-25 9:28 ` Gabriel Niebler
2022-04-25 14:55 ` David Sterba
2022-04-26 7:40 ` Nikolay Borisov
2022-04-26 9:18 ` Gabriel Niebler
2022-04-26 17:52 ` David Sterba
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=730c253b-e595-b898-cf2d-54aa5ade8eba@suse.com \
--to=gniebler@suse.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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