[PATCH] maple_tree: Fix sparse reported issues

Liam Howlett liam.howlett at oracle.com
Wed Jul 13 06:29:39 PDT 2022

* David Hildenbrand <david at redhat.com> [220713 04:34]:
> On 12.07.22 16:24, Liam Howlett wrote:
> > When building with C=1, the maple tree had some rcu type mismatch &
> > locking mismatches in the destroy functions.  There were cosmetic only
> > since this happens after the nodes are removed from the tree.
> > 
> > Fixes: f8acc5e9581e (Maple Tree: add new data structure)
> > Reported-by: kernel test robot <lkp at intel.com>
> > Signed-off-by: Liam R. Howlett <Liam.Howlett at oracle.com>
> Sorry to say, but the fixes become hard to follow (what/where/why). :)
> I guess it's time for a new series soon. Eventually it makes sense to
> send the fixes as reply to the individual problematic patches. (instead
> of fixes to commit ids that are not upstream)
> [yes, I'll do more review soon :) ]

I appreciate the feedback, it's much better than yelling into the void.
I have one more fix in the works - for __vma_adjust() of all functions
so that'll be impossible to follow anyways :)  I'll work on a v11 to
include that last one.


More information about the maple-tree mailing list