Re: [BUG] -next lockdep invalid wait context

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
Subject: Re: [BUG] -next lockdep invalid wait context
From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
Date: Thu, 31 Oct 2024 08:21:36 +0100
Cc: Marco Elver <elver@xxxxxxxxxx>, Vlastimil Babka <vbabka@xxxxxxx>, linux-next@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, kasan-dev@xxxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, sfr@xxxxxxxxxxxxxxxx, longman@xxxxxxxxxx, boqun.feng@xxxxxxxxx, cl@xxxxxxxxx, penberg@xxxxxxxxxx, rientjes@xxxxxxxxxx, iamjoonsoo.kim@xxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx
In-reply-to: <66a745bb-d381-471c-aeee-3800a504f87d@paulmck-laptop>
References: <41619255-cdc2-4573-a360-7794fc3614f7@paulmck-laptop> <e06d69c9-f067-45c6-b604-fd340c3bd612@suse.cz> <ZyK0YPgtWExT4deh@elver.google.com> <66a745bb-d381-471c-aeee-3800a504f87d@paulmck-laptop>

On 2024-10-30 16:10:58 [-0700], Paul E. McKenney wrote:
> 
> So I need to avoid calling kfree() within an smp_call_function() handler?

Yes. No kmalloc()/ kfree() in IRQ context.

> 							Thanx, Paul

Sebastian

Follow-Ups:
- Re: [BUG] -next lockdep invalid wait context
  - From: Vlastimil Babka

References:
- [BUG] -next lockdep invalid wait context
  - From: Paul E. McKenney
- Re: [BUG] -next lockdep invalid wait context
  - From: Vlastimil Babka
- Re: [BUG] -next lockdep invalid wait context
  - From: Marco Elver
- Re: [BUG] -next lockdep invalid wait context
  - From: Paul E. McKenney

Prev by Date: Re: [PATCH v2] mm: add per-order mTHP swpin counters
Next by Date: Re: [BUG] -next lockdep invalid wait context
Previous by thread: Re: [BUG] -next lockdep invalid wait context
Next by thread: Re: [BUG] -next lockdep invalid wait context
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]