[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YJ5qbS2KJcVp+ocY@hirez.programming.kicks-ass.net>
Date: Fri, 14 May 2021 14:17:49 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Liam Howlett <liam.howlett@...cle.com>
Cc: "maple-tree@...ts.infradead.org" <maple-tree@...ts.infradead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Song Liu <songliubraving@...com>,
Davidlohr Bueso <dave@...olabs.net>,
"Paul E . McKenney" <paulmck@...nel.org>,
Matthew Wilcox <willy@...radead.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
David Rientjes <rientjes@...gle.com>,
Axel Rasmussen <axelrasmussen@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>,
Rik van Riel <riel@...riel.com>,
Michel Lespinasse <walken.cr@...il.com>
Subject: Re: [PATCH 26/94] Maple Tree: Add new data structure
On Wed, Apr 28, 2021 at 03:36:02PM +0000, Liam Howlett wrote:
> +static void mas_set_height(struct ma_state *mas)
> +{
> + unsigned int new_flags = mas->tree->ma_flags;
> +
> + new_flags &= ~MAPLE_HEIGHT_MASK;
> + new_flags |= mas->depth << MAPLE_HEIGHT_OFFSET;
> + mas->tree->ma_flags = new_flags;
> +}
This goes sideways when mas->depth is too large; I didn't quickly see an
assertion / range checks for mas->depth anywhere.
Powered by blists - more mailing lists