From: Shakeel Butt <shakeel.butt@linux.dev>
To: Suren Baghdasaryan <surenb@google.com>
Cc: vbabka@suse.cz, akpm@linux-foundation.org, cl@gentwo.org,
rientjes@google.com, roman.gushchin@linux.dev,
harry.yoo@oracle.com, alexei.starovoitov@gmail.com,
usamaarif642@gmail.com, 00107082@163.com, souravpanda@google.com,
kent.overstreet@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/2] slab: mark slab->obj_exts allocation failures unconditionally
Date: Mon, 15 Sep 2025 13:15:19 -0700 [thread overview]
Message-ID: <dia6xv4liysr54vdjfpw3bucbvg3eqh4nn4jh57h5htxev2zy6@rtnakdtz7vjb> (raw)
In-Reply-To: <20250915200918.3855580-3-surenb@google.com>
On Mon, Sep 15, 2025 at 01:09:18PM -0700, Suren Baghdasaryan wrote:
> alloc_slab_obj_exts() should mark failed obj_exts vector allocations
> independent on whether the vector is being allocated for a new or an
> existing slab. Current implementation skips doing this for existing
> slabs. Fix this by marking failed allocations unconditionally.
>
> Fixes: 09c46563ff6d ("codetag: debug: introduce OBJEXTS_ALLOC_FAIL to mark failed slab_ext allocations")
> Reported-by: Shakeel Butt <shakeel.butt@linux.dev>
> Closes: https://lore.kernel.org/all/avhakjldsgczmq356gkwmvfilyvf7o6temvcmtt5lqd4fhp5rk@47gp2ropyixg/
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> Cc: stable@vger.kernel.org # v6.10+
Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
next prev parent reply other threads:[~2025-09-15 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 20:09 [PATCH 0/2] fixes for slab->obj_exts allocation failure handling Suren Baghdasaryan
2025-09-15 20:09 ` [PATCH 1/2] slab: prevent warnings when slab obj_exts vector allocation fails Suren Baghdasaryan
2025-09-15 20:14 ` Shakeel Butt
2025-09-15 20:09 ` [PATCH 2/2] slab: mark slab->obj_exts allocation failures unconditionally Suren Baghdasaryan
2025-09-15 20:15 ` Shakeel Butt [this message]
2025-09-16 12:35 ` [PATCH 0/2] fixes for slab->obj_exts allocation failure handling Vlastimil Babka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dia6xv4liysr54vdjfpw3bucbvg3eqh4nn4jh57h5htxev2zy6@rtnakdtz7vjb \
--to=shakeel.butt@linux.dev \
--cc=00107082@163.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=souravpanda@google.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox