linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, maple-tree@lists.infradead.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 0/3] may miss to set node dead on destroy
Date: Tue, 11 Feb 2025 10:28:53 -0500	[thread overview]
Message-ID: <qtgphm6l4jd3tzrdy2jt5envy3padolzkbjydx6uizomkisq6p@gcfaosnjdgo4> (raw)
In-Reply-To: <20250211081129.xskl56wm2dir2x2f@master>

* Wei Yang <richard.weiyang@gmail.com> [250211 03:11]:
> On Mon, Feb 10, 2025 at 09:31:28AM -0500, Liam R. Howlett wrote:
> >* Wei Yang <richard.weiyang@gmail.com> [250207 20:26]:
> >
> >The subject of this patch set makes the issue sound much more sever than
> >it is.  It currently sounds like a memory leak or a UAF, which isn't the
> >case.
> >
> 
> Not intend to exaggerate the impact.
> 
> Is this one would be better?
> 
>   maple_tree: make sure each node is dead on destroy

Not really, you are fixing two nodes, one isn't even to do with the
destry/dead node.  You are also not making sure each node is dead, but
fixing an issue with the leaf node.

maple_tree: Fix the replacement of a root leaf node ?

> 
> >The root node may remain usable for the duration of the rcu window if
> >it's a leaf node.  The impact is pretty minor - you may see the old data
> >on calls that happen in the same rcu window - which is the case anyways.
> >
> >You should also say maple_tree: in the subject since this is
> >going to linux-mm.  Not a really big deal since each patch in the series
> >specifies the maple tree.
> >
> 
> Thanks, will add it in next version.
> 
> >> Per my understanding, on destroy we should set each node dead. But current
> >> code miss this when the maple tree has only the root node.
> >>     
> >> The reason is mt_destroy_walk() leverage mte_destroy_descend() to set
> >> node dead, but this is skipped since the only root node is a leaf.
> >> 
> >> Patch 1 fixes this.
> >> 
> >> When adding a test case, I found we always get the new value even we leave the
> >> old root node not dead. It turns out we always re-walk the tree in mas_walk().
> >> It looks like a typo on the status check of mas_walk().
> >> 
> >> Patch 2 fixes this.
> >> 
> >> Patch 3 add a test case to assert retrieving new value when overwriting the
> >> whole range to a tree with only root node
> >> 
> >> Wei Yang (3):
> >>   maple_tree: may miss to set node dead on destroy
> >>   maple_tree: restart walk on correct status
> >>   maple_tree: assert retrieving new value on a tree with only root node
> >> 
> >>  lib/maple_tree.c                 |  4 +++-
> >>  tools/testing/radix-tree/maple.c | 24 ++++++++++++++++++++++++
> >>  2 files changed, 27 insertions(+), 1 deletion(-)
> >> 
> >> -- 
> >> 2.34.1
> >> 
> 
> -- 
> Wei Yang
> Help you, Help me


  reply	other threads:[~2025-02-11 15:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08  1:18 Wei Yang
2025-02-08  1:18 ` [PATCH 1/3] maple_tree: " Wei Yang
2025-02-10 14:19   ` Liam R. Howlett
2025-02-11  7:48     ` Wei Yang
2025-02-11 15:23       ` Liam R. Howlett
2025-02-12  0:26         ` Wei Yang
2025-02-08  1:18 ` [PATCH 2/3] maple_tree: restart walk on correct status Wei Yang
2025-02-10 14:20   ` Liam R. Howlett
2025-02-08  1:18 ` [PATCH 3/3] maple_tree: assert retrieving new value on a tree with only root node Wei Yang
2025-02-10 14:18   ` Liam R. Howlett
2025-02-11  8:02     ` Wei Yang
2025-02-11 15:25       ` Liam R. Howlett
2025-02-12  0:41         ` Wei Yang
2025-02-10 14:31 ` [PATCH 0/3] may miss to set node dead on destroy Liam R. Howlett
2025-02-11  8:11   ` Wei Yang
2025-02-11 15:28     ` Liam R. Howlett [this message]
2025-02-12  0:49       ` Wei Yang
2025-02-12  0:55       ` Wei Yang
2025-03-04 12:07         ` Wei Yang
2025-03-04 14:45           ` Liam R. Howlett
2025-03-05  0:32             ` Wei Yang

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=qtgphm6l4jd3tzrdy2jt5envy3padolzkbjydx6uizomkisq6p@gcfaosnjdgo4 \
    --to=liam.howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=maple-tree@lists.infradead.org \
    --cc=richard.weiyang@gmail.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