From: Peng Zhang <zhangpeng.00@bytedance.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Liam.Howlett@oracle.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, maple-tree@lists.infradead.org
Subject: Re: [PATCH v2 0/3] Some fixes and cleanup for maple tree.
Date: Wed, 5 Apr 2023 17:53:44 +0800 [thread overview]
Message-ID: <1d3b071f-ead7-4431-c9f8-c712e7c8bdc6@bytedance.com> (raw)
In-Reply-To: <20230404132702.9240f3a77d0c00fca4b9bf55@linux-foundation.org>
在 2023/4/5 04:27, Andrew Morton 写道:
> On Tue, 14 Mar 2023 20:42:00 +0800 Peng Zhang <zhangpeng.00@bytedance.com> wrote:
>
>> Some fixes and clean up for maple tree.
>>
>> The bug fixed by [PATCH v2 1/3] does not seem to be triggered due to some
>> coincidences, because now the implementation of mtree_lookup_walk() scans
>> pivots one by one and exits the loop early. The test cases for the bugs fixed by
>> [PATCH v2 3/3] are difficult to write. If I think of how to write them later,
>> I will send them out. So I send out the second edition first.
> Do we feel that any of these should be backported into -stable kernels?
> [3/3] looks to be a candidate for this?
Both [1/3] and [3/3] can be sent to the stable kernel, do I need to do anything?
next prev parent reply other threads:[~2023-04-05 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 12:42 Peng Zhang
2023-03-14 12:42 ` [PATCH v2 1/3] maple_tree: Fix get wrong data_end in mtree_lookup_walk() Peng Zhang
2023-03-14 12:42 ` [PATCH v2 2/3] maple_tree: Simplify mas_wr_node_walk() Peng Zhang
2023-03-14 12:42 ` [PATCH v2 3/3] maple_tree: Fix a potential concurrency bug in RCU mode Peng Zhang
2023-04-04 7:56 ` [PATCH v2 0/3] Some fixes and cleanup for maple tree Peng Zhang
2023-04-04 20:27 ` Andrew Morton
2023-04-05 0:49 ` Liam R. Howlett
2023-04-05 9:53 ` Peng Zhang [this message]
2023-04-05 17:49 ` Liam R. Howlett
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=1d3b071f-ead7-4431-c9f8-c712e7c8bdc6@bytedance.com \
--to=zhangpeng.00@bytedance.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 \
/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