From: David Hildenbrand <david@redhat.com>
To: Liam Howlett <liam.howlett@oracle.com>,
"maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] maple_tree: Make mas_prealloc() error checking more generic
Date: Tue, 21 Jun 2022 11:09:50 +0200 [thread overview]
Message-ID: <f7e9b2a7-9ec8-3922-ee06-eea0e26a26dd@redhat.com> (raw)
In-Reply-To: <20220615174213.738849-1-Liam.Howlett@oracle.com>
On 15.06.22 19:42, Liam Howlett wrote:
> Return the error regardless of what it is. This is a safer option.
>
> Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
> ---
> lib/maple_tree.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/lib/maple_tree.c b/lib/maple_tree.c
> index f413b6f0da2b..89ff5ef7ee28 100644
> --- a/lib/maple_tree.c
> +++ b/lib/maple_tree.c
> @@ -5670,16 +5670,15 @@ void mas_store_prealloc(struct ma_state *mas, void *entry)
> */
> int mas_preallocate(struct ma_state *mas, void *entry, gfp_t gfp)
> {
> -
> mas_set_alloc_req(mas, 1 + mas_mt_height(mas) * 3);
> mas_alloc_nodes(mas, gfp);
> - if (likely(mas->node != MA_ERROR(-ENOMEM)))
> + if (likely(!mas_is_err(mas)))
> return 0;
>
> mas_set_alloc_req(mas, 0);
> mas_destroy(mas);
> mas->node = MAS_START;
> - return -ENOMEM;
> + return xa_err(mas->node);
> }
>
> /*
Liam, (as asked privately before, I was just too busy to respond :) )
once all known issues are fixed, can we have a new version posted to
ease review? That would make my life easier to see what needs review and
in which order patches apply. Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-06-21 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 17:42 Liam Howlett
2022-06-21 9:09 ` David Hildenbrand [this message]
2022-06-21 13:22 ` Liam Howlett
2022-06-21 20:38 ` Andrew Morton
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=f7e9b2a7-9ec8-3922-ee06-eea0e26a26dd@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=liam.howlett@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