Re: [PATCH] memcg: Don't call schedule_work when no spinning is allowed

[Andrew Morton]

On Mon, 31 Aug 2026 16:43:39 -0700 David Stevens <stevensd@xxxxxxxxxx> wrote:

> Memcg charging can be done from any context, but calling schedule_work()
> isn't safe from an NMI.

Who does that.  bpf, IIRC?

> If memory.high is breached from a context where
> spinning isn't allowed, use irq_work to schedule the reclaim work.
> 
> Fixes: 3ac4638a734a ("memcg: make memcg_rstat_updated nmi safe")

Can anything actually hit this?  IOW, should we backport it?

> Signed-off-by: David Stevens <stevensd@xxxxxxxxxx>