From: yangerkun <yangerkun@huaweicloud.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, chuck.lever@oracle.com,
brauner@kernel.org
Subject: Re: [PATCH 2/2] test_maple_tree: Test exhausted upper limit of mtree_alloc_cyclic()
Date: Tue, 17 Dec 2024 19:41:36 +0800 [thread overview]
Message-ID: <0737acaa-ba88-764c-d8ad-376b28b988e3@huaweicloud.com> (raw)
In-Reply-To: <20241216190113.1226145-3-Liam.Howlett@oracle.com>
在 2024/12/17 3:01, Liam R. Howlett 写道:
> From: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
>
> When the upper bound of the search is exhausted, the maple state may be
> returned in an error state of -EBUSY. This means maple state needs to
> be reset before the second search in mas_alloc_cylic() to ensure the
> search happens. This test ensures the issue is not recreated.
>
> Cc: Yang Erkun <yangerkun@huaweicloud.com>
> Cc: chuck.lever@oracle.com
> Cc: brauner@kernel.org
> Signed-off-by: Liam R. Howlett <Liam.Howlett@Oracle.com>
> ---
> lib/test_maple_tree.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
Thanks for the testcase!
Reviewed-by: Yang Erkun <yangerkun@huawei.com>
> diff --git a/lib/test_maple_tree.c b/lib/test_maple_tree.c
> index 72bda304b5952..13e2a10d7554d 100644
> --- a/lib/test_maple_tree.c
> +++ b/lib/test_maple_tree.c
> @@ -3738,6 +3738,34 @@ static noinline void __init alloc_cyclic_testing(struct maple_tree *mt)
> }
>
> mtree_destroy(mt);
> +
> + /*
> + * Issue with reverse search was discovered
> + * https://lore.kernel.org/all/20241216060600.287B4C4CED0@smtp.kernel.org/
> + * Exhausting the allocation area and forcing the search to wrap needs a
> + * mas_reset() in mas_alloc_cyclic().
> + */
> + next = 0;
> + mt_init_flags(mt, MT_FLAGS_ALLOC_RANGE);
> + for (int i = 0; i < 1023; i++) {
> + mtree_alloc_cyclic(mt, &location, mt, 2, 1024, &next, GFP_KERNEL);
> + MT_BUG_ON(mt, i != location - 2);
> + MT_BUG_ON(mt, i != next - 3);
> + MT_BUG_ON(mt, mtree_load(mt, location) != mt);
> + }
> + mtree_erase(mt, 123);
> + MT_BUG_ON(mt, mtree_load(mt, 123) != NULL);
> + mtree_alloc_cyclic(mt, &location, mt, 2, 1024, &next, GFP_KERNEL);
> + MT_BUG_ON(mt, 123 != location);
> + MT_BUG_ON(mt, 124 != next);
> + MT_BUG_ON(mt, mtree_load(mt, location) != mt);
> + mtree_erase(mt, 100);
> + mtree_alloc_cyclic(mt, &location, mt, 2, 1024, &next, GFP_KERNEL);
> + MT_BUG_ON(mt, 100 != location);
> + MT_BUG_ON(mt, 101 != next);
> + MT_BUG_ON(mt, mtree_load(mt, location) != mt);
> + mtree_destroy(mt);
> +
> /* Overflow test */
> next = ULONG_MAX - 1;
> ret = mtree_alloc_cyclic(mt, &location, mt, 2, ULONG_MAX, &next, GFP_KERNEL);
prev parent reply other threads:[~2024-12-17 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 19:01 [PATCH 0/2] Fix mas_alloc_cyclic retry Liam R. Howlett
2024-12-16 19:01 ` [PATCH 1/2] maple_tree: Fix mas_alloc_cyclic() second search Liam R. Howlett
2024-12-17 11:27 ` yangerkun
2024-12-16 19:01 ` [PATCH 2/2] test_maple_tree: Test exhausted upper limit of mtree_alloc_cyclic() Liam R. Howlett
2024-12-17 11:41 ` yangerkun [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=0737acaa-ba88-764c-d8ad-376b28b988e3@huaweicloud.com \
--to=yangerkun@huaweicloud.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.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