maple_tree: Don't set a new maximum on the node when not reusing nodes

Message ID 20221107163857.867377-1-Liam.Howlett@oracle.com
State New
Headers
Series maple_tree: Don't set a new maximum on the node when not reusing nodes |

Commit Message

Liam R. Howlett Nov. 7, 2022, 4:39 p.m. UTC
  In RCU mode, the node limits were being updated to the last pivot which
may not be correct and would cause the metadata to be set when it
shouldn't.  Fix this by not setting a new limit in this case.

Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
 lib/maple_tree.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
  

Patch

diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index acc7123347c7..221f66d7cb3c 100644
--- a/lib/maple_tree.c
+++ b/lib/maple_tree.c
@@ -3608,8 +3608,7 @@  static inline int mas_commit_b_node(struct ma_wr_state *wr_mas,
 	node = mas_pop_node(wr_mas->mas);
 	node->parent = mas_mn(wr_mas->mas)->parent;
 	wr_mas->mas->node = mt_mk_node(node, b_type);
-	mab_mas_cp(b_node, 0, b_end, wr_mas->mas, true);
-
+	mab_mas_cp(b_node, 0, b_end, wr_mas->mas, false);
 	mas_replace(wr_mas->mas, false);
 reuse_node:
 	mas_update_gap(wr_mas->mas);