From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, cl@gentwo.org, rientjes@google.com,
roman.gushchin@linux.dev, harry.yoo@oracle.com,
shakeel.butt@linux.dev, 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
Subject: Re: [PATCH 0/2] fixes for slab->obj_exts allocation failure handling
Date: Tue, 16 Sep 2025 14:35:28 +0200 [thread overview]
Message-ID: <01108e4b-9586-4147-9b8a-c3435f6a98d6@suse.cz> (raw)
In-Reply-To: <20250915200918.3855580-1-surenb@google.com>
On 9/15/25 22:09, Suren Baghdasaryan wrote:
> Fixes for several issues noticed by Shakeel pertaining to slab->obj_exts
> allocation failure handling in [1].
>
> Patchset is based on mm-new.
>
> Please route it via vbabka/slab.git as it's relevant to Alexei's patches
> in that branch.
Thanks, added to slab/for-6.18/fixes
> [1] https://lore.kernel.org/all/jftidhymri2af5u3xtcqry3cfu6aqzte3uzlznhlaylgrdztsi@5vpjnzpsemf5/
>
> Suren Baghdasaryan (2):
> slab: prevent warnings when slab obj_exts vector allocation fails
> slab: mark slab->obj_exts allocation failures unconditionally
>
> mm/slab.h | 8 ++++++--
> mm/slub.c | 3 +--
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
>
> base-commit: 9a9318f95d63805868bd21e1381d68c3a75d03a7
prev parent reply other threads:[~2025-09-16 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 20:09 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
2025-09-16 12:35 ` Vlastimil Babka [this message]
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=01108e4b-9586-4147-9b8a-c3435f6a98d6@suse.cz \
--to=vbabka@suse.cz \
--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=shakeel.butt@linux.dev \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
/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