[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zy5OX5Wy0LsFPdjO@Boquns-Mac-mini.local>
Date: Fri, 8 Nov 2024 09:46:07 -0800
From: Boqun Feng <boqun.feng@...il.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, "Paul E. McKenney" <paulmck@...nel.org>,
Marco Elver <elver@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Tomas Gleixner <tglx@...utronix.de>,
Vlastimil Babka <vbabka@...e.cz>, akpm@...ux-foundation.org,
cl@...ux.com, iamjoonsoo.kim@....com, longman@...hat.com,
penberg@...nel.org, rientjes@...gle.com, sfr@...b.auug.org.au
Subject: Re: [PATCH v3 0/4] scftorture: Avoid kfree from IRQ context.
On Fri, Nov 08, 2024 at 11:39:30AM +0100, Sebastian Andrzej Siewior wrote:
> Hi,
>
> Paul reported kfree from IRQ context in scftorture which is noticed by
> lockdep since the recent PROVE_RAW_LOCK_NESTING switch.
>
> The last patch in this series adresses the issues, the other things
> happened on the way.
>
> v2...v3:
> - The clean up on module exit must not be done with thread numbers.
> Reported by Boqun Feng.
> - Move the clean up on module exit prior to torture_cleanup_end().
> Reported by Paul.
>
> v1...v2:
> - Remove kfree_bulk(). I get more invocations per report without it.
> - Pass `cpu' to scf_cleanup_free_list in scftorture_invoker() instead
> of scfp->cpu. The latter is the thread number which can be larger
> than the number CPUs leading to a crash in such a case. Reported by
> Boqun Feng.
> - Clean up the per-CPU lists on module exit. Reported by Boqun Feng.
>
> Sebastian
>
For the whole series:
Reviewed-by: Boqun Feng <boqun.feng@...il.com>
Tested-by: Boqun Feng <boqun.feng@...il.com>
Regards,
Boqun
Powered by blists - more mailing lists