[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241107111821.3417762-1-bigeasy@linutronix.de>
Date: Thu, 7 Nov 2024 12:13:05 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: kasan-dev@...glegroups.com,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Cc: "Paul E. McKenney" <paulmck@...nel.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: [PATCH v2 0/3] scftorture: Avoid kfree from IRQ context.
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.
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