[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9079817-72bf-4f6f-ad4a-b423a7d2e0b4@paulmck-laptop>
Date: Thu, 7 Nov 2024 11:05:24 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Boqun Feng <boqun.feng@...il.com>,
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 v2 0/3] scftorture: Avoid kfree from IRQ context.
On Thu, Nov 07, 2024 at 12:13:05PM +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.
For the series:
Tested-by: Paul E. McKenney <paulmck@...nel.org>
> 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
>
Powered by blists - more mailing lists