Re: [PATCH v2] mm/kmemleak: Avoid scanning potential huge holes

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

To: Catalin Marinas <catalin.marinas@xxxxxxx>
Subject: Re: [PATCH v2] mm/kmemleak: Avoid scanning potential huge holes
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 31 Jan 2022 16:51:41 -0800
Cc: Lang Yu <lang.yu@xxxxxxx>, linux-mm@xxxxxxxxx, David Hildenbrand <david@xxxxxxxxxx>, Oscar Salvador <osalvador@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <YfREFu1sAJ+Yn6jy@arm.com>
References: <20211108140029.721144-1-lang.yu@amd.com> <YfREFu1sAJ+Yn6jy@arm.com>

On Fri, 28 Jan 2022 19:29:26 +0000 Catalin Marinas <catalin.marinas@xxxxxxx> wrote:

> Acked-by: Catalin Marinas <catalin.marinas@xxxxxxx>

Thanks.

I think this deserves a cc:stable?  Triggering the soft lockup detector
is bad behavior.

Follow-Ups:
- Re: [PATCH v2] mm/kmemleak: Avoid scanning potential huge holes
  - From: Catalin Marinas

References:
- [PATCH v2] mm/kmemleak: Avoid scanning potential huge holes
  - From: Lang Yu
- Re: [PATCH v2] mm/kmemleak: Avoid scanning potential huge holes
  - From: Catalin Marinas

Prev by Date: [PATCH 2/2] mm/memcg: retrieve parent memcg from css.parent
Next by Date: Re: [PATCH v1] drivers/base/memory: add memory block to memory group after registration succeeded
Previous by thread: Re: [PATCH v2] mm/kmemleak: Avoid scanning potential huge holes
Next by thread: Re: [PATCH v2] mm/kmemleak: Avoid scanning potential huge holes
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]

Powered by Linux