[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250521142521.3033264-1-usamaarif642@gmail.com>
Date: Wed, 21 May 2025 15:25:21 +0100
From: Usama Arif <usamaarif642@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
surenb@...gle.com
Cc: hannes@...xchg.org,
shakeel.butt@...ux.dev,
vlad.wing@...il.com,
linux-mm@...ck.org,
kent.overstreet@...ux.dev,
cl@...two.org,
rientjes@...gle.com,
vbabka@...e.cz,
roman.gushchin@...ux.dev,
harry.yoo@...cle.com,
linux-kernel@...r.kernel.org,
kernel-team@...a.com,
Usama Arif <usamaarif642@...il.com>
Subject: [PATCH] mm: slub: do not warn when allocating slab obj extensions fails
In memory bound systems, a large number of warnings for failing this
allocation repeatedly may mask any real issues in the system
during memory pressure being reported in dmesg. Failing this
allocation is not indicative of a bug, so remove the warning.
Signed-off-by: Usama Arif <usamaarif642@...il.com>
Reported-by: Vlad Poenaru <vlad.wing@...il.com>
Closes: https://lore.kernel.org/all/17fab2d6-5a74-4573-bcc3-b75951508f0a@gmail.com/
---
v1 -> v2:
- remove the warning completely. We will have a way in the
future to indicate that the mem alloc profile is inaccurate.
---
mm/slub.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index dc9e729e1d26..06ab9a558b73 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -2102,9 +2102,7 @@ prepare_slab_obj_exts_hook(struct kmem_cache *s, gfp_t flags, void *p)
slab = virt_to_slab(p);
if (!slab_obj_exts(slab) &&
- WARN(alloc_slab_obj_exts(slab, s, flags, false),
- "%s, %s: Failed to create slab extension vector!\n",
- __func__, s->name))
+ alloc_slab_obj_exts(slab, s, flags, false))
return NULL;
return slab_obj_exts(slab) + obj_to_index(s, slab, p);
--
2.47.1
Powered by blists - more mailing lists