From: "Vishal Moola (Fractile)" <vishal.moola@gmail.com>
To: "Liam R. Howlett (Google)" <liam@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] tools/testing/shared: catch a failed posix_memalign()
Date: Tue, 20 Oct 2026 16:10:08 +0100 [thread overview]
Message-ID: <ateEUAMoDCgiHrrT@C422HJQPQG-Fractile> (raw)
In-Reply-To: <20261020033128.1934349-1-liam@infradead.org>
On Mon, Oct 19, 2026 at 11:31:28PM -0400, Liam R. Howlett (Google) wrote:
> posix_memalign() returns zero or a positive error number and never sets
> errno, so the checks for a negative return in kmem_cache_alloc_lru() and
> kmem_cache_alloc_bulk() is not possible. A failed aligned allocation
> carries on with the pointer unset, into the constructor or the memset().
>
> Test for any non-zero return.
>
> Signed-off-by: Liam R. Howlett (Google) <liam@infradead.org>
Reviewed-by: Vishal Moola (Fractile) <vishal.moola@gmail.com>
It's not really a big deal, but seems this was introduced in commit
8801c35c3672c ("tools: fix -Wunused-result in linux.c"), so +CC the
author Shuah Khan.
> tools/testing/shared/linux.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/shared/linux.c b/tools/testing/shared/linux.c
> index e0a0693df08f5..a37d2f86d3254 100644
> --- a/tools/testing/shared/linux.c
> +++ b/tools/testing/shared/linux.c
> @@ -83,7 +83,7 @@ void *kmem_cache_alloc_lru(struct kmem_cache *cachep, struct list_lru *lru,
> } else {
> pthread_mutex_unlock(&cachep->lock);
> if (cachep->align) {
> - if (posix_memalign(&p, cachep->align, cachep->size) < 0)
> + if (posix_memalign(&p, cachep->align, cachep->size))
> return NULL;
> } else {
> p = malloc(cachep->size);
> @@ -191,7 +191,7 @@ bool kmem_cache_alloc_bulk(struct kmem_cache *cachep, gfp_t gfp, size_t size,
>
> if (cachep->align) {
> if (posix_memalign(&p[i], cachep->align,
> - cachep->size) < 0)
> + cachep->size))
> break;
> } else {
> p[i] = malloc(cachep->size);
> --
> 2.47.3
>
prev parent reply other threads:[~2026-10-20 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 3:31 Liam R. Howlett (Google)
2026-10-20 9:05 ` Lorenzo Stoakes (ARM)
2026-10-20 15:10 ` Vishal Moola (Fractile) [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=ateEUAMoDCgiHrrT@C422HJQPQG-Fractile \
--to=vishal.moola@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
/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
all inboxes | Powered by JetHome®