From: Jason Gunthorpe <jgg@ziepe.ca>
To: luoqing <l1138897701@163.com>
Cc: Leon Romanovsky <leon@kernel.org>, Kees Cook <kees@kernel.org>,
Mark Zhang <markzhang@nvidia.com>, luoqing <luoqing@kylinos.cn>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rdma: infiniband: Added __alloc_cq request value Return value non-zero value determination
Date: Tue, 26 May 2026 09:23:29 -0300 [thread overview]
Message-ID: <20260526122329.GC2487554@ziepe.ca> (raw)
In-Reply-To: <20260526091816.1873077-1-l1138897701@163.com>
On Tue, May 26, 2026 at 05:18:16PM +0800, luoqing wrote:
> From: luoqing <luoqing@kylinos.cn>
>
> Currently, when __alloc_cq allocates memory for an InfiniBand Completion Queue (ib_cq) object,
> it uses memory allocation functions that may not guarantee zero-initialization under certain error paths or memory pressure conditions.
> If the allocated ib_cq object contains non-zero garbage data due to incomplete initialization,
> the function may return a non-NULL pointer even though the object is not in a valid state. This can lead to undefined behavior,
> memory corruption, and potential kernel crashes when the driver subsequently accesses uninitialized fields.
>
> This patch adds explicit validation to ensure that the allocated ib_cq object is properly zeroed before being considered valid.
> If the object fails the zero-check (i.e., contains non-zero bytes beyond expected initialized fields),
> the function returns an error code (e.g., -ENOMEM or -EINVAL), logs a warning message, and prevents further usage of the corrupted CQ.
>
> Signed-off-by: luoqing <luoqing@kylinos.cn>
> ---
> drivers/infiniband/core/cq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/core/cq.c b/drivers/infiniband/core/cq.c
> index 3d7b6cddd131..756bc33c850d 100644
> --- a/drivers/infiniband/core/cq.c
> +++ b/drivers/infiniband/core/cq.c
> @@ -224,7 +224,7 @@ struct ib_cq *__ib_alloc_cq(struct ib_device *dev, void *private, int nr_cqe,
> return ERR_PTR(-EINVAL);
>
> cq = rdma_zalloc_drv_obj(dev, ib_cq);
> - if (!cq)
> + if (unlikely(ZERO_OR_NULL_PTR(cq)))
> return ERR_PTR(ret);
Wow, this entire report is unintelligible.
ZERO_OR_NULL_PTR() has nothing to do with the memory contents.
Jason
next prev parent reply other threads:[~2026-05-26 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 9:18 luoqing
2026-05-26 12:23 ` Jason Gunthorpe [this message]
2026-05-28 6:54 ` luoqing
2026-05-28 13:09 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2025-04-07 9:33 luoqing
2025-04-07 16:25 ` Jason Gunthorpe
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=20260526122329.GC2487554@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=kees@kernel.org \
--cc=l1138897701@163.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=luoqing@kylinos.cn \
--cc=markzhang@nvidia.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
all inboxes | Powered by JetHome®