From: Jason Gunthorpe <jgg@nvidia.com>
To: Qianqiang Liu <qianqiang.liu@163.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] RDMA/nldev: Fix NULL pointer dereferences issue in rdma_nl_notify_event
Date: Fri, 4 Oct 2024 17:13:02 -0300 [thread overview]
Message-ID: <20241004201302.GA3317055@nvidia.com> (raw)
In-Reply-To: <Zva71Yf3F94uxi5A@iZbp1asjb3cy8ks0srf007Z>
On Fri, Sep 27, 2024 at 10:06:13PM +0800, Qianqiang Liu wrote:
> nlmsg_put() may return a NULL pointer assigned to nlh, which will later
> be dereferenced in nlmsg_end().
>
> Fixes: 9cbed5aab5ae ("RDMA/nldev: Add support for RDMA monitoring")
> Signed-off-by: Qianqiang Liu <qianqiang.liu@163.com>
> ---
> Changes since v1:
> - Add Fixes tag
> ---
> drivers/infiniband/core/nldev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/infiniband/core/nldev.c b/drivers/infiniband/core/nldev.c
> index 39f89a4b86498..7dc8e2ec62cc8 100644
> --- a/drivers/infiniband/core/nldev.c
> +++ b/drivers/infiniband/core/nldev.c
> @@ -2816,6 +2816,8 @@ int rdma_nl_notify_event(struct ib_device *device, u32 port_num,
> nlh = nlmsg_put(skb, 0, 0,
> RDMA_NL_GET_TYPE(RDMA_NL_NLDEV, RDMA_NLDEV_CMD_MONITOR),
> 0, 0);
> + if (!nlh)
> + goto err_free;
It doesn't look to me like nlmsg_put can fail in this usage, but we
should probbaly put the if to avoid getting static checkers warning on
it.
Applied to for-rc, thanks
Jason
next prev parent reply other threads:[~2024-10-04 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 14:34 [PATCH] RDMA/nldev: Fix NULL pointer dereferences issue in rdma_nl_notify_event Qianqiang Liu
2024-09-27 14:06 ` [PATCH v2] " Qianqiang Liu
2024-10-04 20:13 ` Jason Gunthorpe [this message]
2024-10-09 14:31 ` Dan Carpenter
2024-10-09 14:30 ` [PATCH] " Dan Carpenter
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=20241004201302.GA3317055@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=qianqiang.liu@163.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