From: Peng Zhang <perlyzhang@gmail.com>
To: "Liam R. Howlett" <Liam.Howlett@Oracle.com>,
Peng Zhang <zhangpeng.00@bytedance.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, maple-tree@lists.infradead.org
Subject: Re: [PATCH 1/2] maple_tree: Add a test case to check maple_alloc
Date: Mon, 10 Apr 2023 21:02:04 +0800 [thread overview]
Message-ID: <d4b49df5-0f17-15f1-a077-3a30beb64386@gmail.com> (raw)
In-Reply-To: <20230410124144.ouhhnmfoipkqtveu@revolver>
在 2023/4/10 20:41, Liam R. Howlett 写道:
> * Peng Zhang <zhangpeng.00@bytedance.com> [230407 00:09]:
>> Add a test case to check whether the number of maple_alloc structures is
>> actually equal to mas->alloc->total.
> Thanks for the test case. Can you please send the code to fix the issue
> first in the future? This way the verification code can be used to
> bisect any issues.
Ok, I will exchange the order of the two patches in the next version.
>
>> Signed-off-by: Peng Zhang <zhangpeng.00@bytedance.com>
>> ---
>> tools/testing/radix-tree/maple.c | 24 ++++++++++++++++++++++++
>> 1 file changed, 24 insertions(+)
>>
>> diff --git a/tools/testing/radix-tree/maple.c b/tools/testing/radix-tree/maple.c
>> index 958ee9bdb316..26389e0dcfff 100644
>> --- a/tools/testing/radix-tree/maple.c
>> +++ b/tools/testing/radix-tree/maple.c
>> @@ -55,6 +55,28 @@ struct rcu_reader_struct {
>> struct rcu_test_struct2 *test;
>> };
>>
>> +static int get_alloc_node_count(struct ma_state *mas)
>> +{
>> + int count = 1;
>> + struct maple_alloc *node = mas->alloc;
>> +
>> + if (!node || ((unsigned long)node & 0x1))
>> + return 0;
>> + while (node->node_count) {
>> + count += node->node_count;
>> + node = node->slot[0];
>> + }
>> + return count;
>> +}
>> +
>> +static void check_mas_alloc_node_count(struct ma_state *mas)
>> +{
>> + mas_node_count_gfp(mas, MAPLE_ALLOC_SLOTS + 1, GFP_KERNEL);
>> + mas_node_count_gfp(mas, MAPLE_ALLOC_SLOTS + 3, GFP_KERNEL);
>> + MT_BUG_ON(mas->tree, get_alloc_node_count(mas) != mas->alloc->total);
>> + mas_destroy(mas);
>> +}
>> +
>> /*
>> * check_new_node() - Check the creation of new nodes and error path
>> * verification.
>> @@ -69,6 +91,8 @@ static noinline void check_new_node(struct maple_tree *mt)
>>
>> MA_STATE(mas, mt, 0, 0);
>>
>> + check_mas_alloc_node_count(&mas);
>> +
>> /* Try allocating 3 nodes */
>> mtree_lock(mt);
>> mt_set_non_kernel(0);
>> --
>> 2.20.1
>>
prev parent reply other threads:[~2023-04-10 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 4:07 [PATCH 1/2] maple_tree: Add a test case to check maple_alloc Peng Zhang
2023-04-07 4:07 ` [PATCH 2/2] maple_tree: Fix a potential memory leak, OOB access, or other unpredictable bug Peng Zhang
2023-04-10 12:43 ` Liam R. Howlett
2023-04-10 12:58 ` Peng Zhang
2023-04-10 13:12 ` Liam R. Howlett
2023-04-10 13:28 ` Peng Zhang
2023-04-10 15:00 ` Liam R. Howlett
2023-04-10 15:23 ` Peng Zhang
2023-04-08 3:16 ` [PATCH 1/2] maple_tree: Add a test case to check maple_alloc Liam R. Howlett
2023-04-08 3:22 ` Liam R. Howlett
2023-04-10 12:41 ` Liam R. Howlett
2023-04-10 13:02 ` Peng Zhang [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=d4b49df5-0f17-15f1-a077-3a30beb64386@gmail.com \
--to=perlyzhang@gmail.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=zhangpeng.00@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.