From: Andrew Morton <akpm@linux-foundation.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: Liam.Howlett@oracle.com, maple-tree@lists.infradead.org,
linux-mm@kvack.org
Subject: Re: [PATCH v5 0/5] refine storing null
Date: Thu, 31 Oct 2024 17:20:05 -0700 [thread overview]
Message-ID: <20241031172005.b129619e6832e23db8e9f21e@linux-foundation.org> (raw)
In-Reply-To: <20241031231627.14316-1-richard.weiyang@gmail.com>
On Thu, 31 Oct 2024 23:16:22 +0000 Wei Yang <richard.weiyang@gmail.com> wrote:
> The original thread[1] thoughts it is a problem in mas_new_root(). But after
> discussion, this should be an improvement on storing NULL.
I hate to be a bureaucrat, but that isn't a very satisfying [0/N].
>
> [1]: https://lkml.kernel.org/r/20241015233909.23592-1-richard.weiyang@gmail.com
From here I extracted "When overwriting the whole range with NULL,
current behavior is not correct", but that's still very thin. What is
incorrect about it and what is the impact of all of this to Linux users?
next prev parent reply other threads:[~2024-11-01 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 23:16 [PATCH v5 0/5] refine storing null Wei Yang
2024-10-31 23:16 ` [PATCH v5 1/5] maple_tree: print empty for an empty tree on mt_dump() Wei Yang
2024-10-31 23:16 ` [PATCH v5 2/5] maple_tree: the return value of mas_root_expand() is not used Wei Yang
2024-10-31 23:16 ` [PATCH v5 3/5] maple_tree: not necessary to check index/last again Wei Yang
2024-10-31 23:16 ` [PATCH v5 4/5] maple_tree: refine mas_store_root() on storing NULL Wei Yang
2024-11-01 14:59 ` Liam R. Howlett
2024-11-01 18:41 ` Andrew Morton
2024-10-31 23:16 ` [PATCH v5 5/5] maple_tree: add a test checking storing null Wei Yang
2024-11-01 3:37 ` Andrew Morton
2024-11-03 22:46 ` Wei Yang
2024-11-01 0:20 ` Andrew Morton [this message]
2024-11-01 14:52 ` [PATCH v5 0/5] refine " Liam R. Howlett
2024-11-03 23:09 ` 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=20241031172005.b129619e6832e23db8e9f21e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--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