From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF0292D8368; Fri, 4 Jul 2025 16:48:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751647690; cv=none; b=lq6PYEMoQa49AC3KIzwm5yyPlkrMv9vuA5f0lQCE4j7C9Vgrwe+gpMd3expd3NLhJ5PnmfUdvytKRlehvUXzgUP89z9qilWtmQ7vCotVryKYBk3MoQ2YSehSlFhgx8NFczmqWzK33P8b1pn09sVnj0I5hNwsQSbDF/Zd3uVY9cU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751647690; c=relaxed/simple; bh=BMXgAQlDKN+mET+jMsDybdF+/EB3t5j/i7lP7yLuKdY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=cUTiO33A9xiH2aGhigpC7NcN8XvNgePZ9y/cO1ysZeFN/XZolHZcH1nBgJjXiEvZvn0/PuNGw+vcvmUkfgzjwzCaxd0TQFX9HtlOYiCcXfSTCGgj9lq4cPucQlFVMNJ6JESaRF9Sx3k4UYLRR7H+6faKoHI8SRzXQHzjylmO6ZY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=rx4+MXeP; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="rx4+MXeP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 44375C4CEE3; Fri, 4 Jul 2025 16:48:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1751647690; bh=BMXgAQlDKN+mET+jMsDybdF+/EB3t5j/i7lP7yLuKdY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=rx4+MXeP/7v+RpQ4g0tuv5M13L0hFoFo8Jj0R9y1UD7zOMHZYpliSXMjFSPKFdy/J BAtxH+iDerzV+oBeewMDbWa3wsbD5H+8pI+UPRxYlly7eBJhaeabD10QH5PEPBqweg 4+0PaGreGR0OzrkMZW5DWUhrFO2gL1h4n6MO6d5aK7TzG22INCHDUJdWSbLbWKNgP7 722DVPdgkNHpA4t8VM7gVyjVxVEpUTm++T/AJDDDaky/A+EhcnSSfMTbtR+MzU77gv AmnC2yOFFRPsMmdOJQBpYG3yDDlgzjPAGtpHCJfd/7LheenciRa3oONLqnxmPxPCZa 9F3owIl/Thh7Q== Date: Fri, 4 Jul 2025 17:48:04 +0100 From: Simon Horman To: Leon Romanovsky Cc: Jason Gunthorpe , Stav Aviram , Andrew Lunn , Eric Dumazet , Jakub Kicinski , linux-rdma@vger.kernel.org, Mark Bloch , netdev@vger.kernel.org, Paolo Abeni , Saeed Mahameed , Tariq Toukan , Michal Swiatkowski Subject: Re: [PATCH mlx5-next v1] net/mlx5: Check device memory pointer before usage Message-ID: <20250704164804.GK41770@horms.kernel.org> References: <20250701193858.GA41770@horms.kernel.org> <20250702082847.GH6278@unreal> <20250702140735.GE41770@horms.kernel.org> <20250702174953.GJ6278@unreal> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250702174953.GJ6278@unreal> On Wed, Jul 02, 2025 at 08:49:53PM +0300, Leon Romanovsky wrote: > On Wed, Jul 02, 2025 at 03:07:35PM +0100, Simon Horman wrote: > > On Wed, Jul 02, 2025 at 11:28:47AM +0300, Leon Romanovsky wrote: > > > On Tue, Jul 01, 2025 at 08:38:58PM +0100, Simon Horman wrote: > > > > On Tue, Jul 01, 2025 at 03:08:12PM +0300, Leon Romanovsky wrote: > > > > > From: Stav Aviram > > > > > > > > > > Add a NULL check before accessing device memory to prevent a crash if > > > > > dev->dm allocation in mlx5_init_once() fails. > > > > > > > > > > Fixes: c9b9dcb430b3 ("net/mlx5: Move device memory management to mlx5_core") > > > > > Signed-off-by: Stav Aviram > > > > > Signed-off-by: Leon Romanovsky > > > > > --- > > > > > Changelog: > > > > > v1: > > > > > * Removed extra IS_ERR(dm) check. > > > > > v0: > > > > > https://lore.kernel.org/all/e389fa6ef075af1049cd7026b912d736ebe3ad23.1751279408.git.leonro@nvidia.com > > > > > --- > > > > > drivers/infiniband/hw/mlx5/dm.c | 2 +- > > > > > drivers/net/ethernet/mellanox/mlx5/core/lib/dm.c | 4 ++-- > > > > > drivers/net/ethernet/mellanox/mlx5/core/main.c | 2 +- > > > > > 3 files changed, 4 insertions(+), 4 deletions(-) > > > > > > > > > > diff --git a/drivers/infiniband/hw/mlx5/dm.c b/drivers/infiniband/hw/mlx5/dm.c > > > > > index b4c97fb62abf..9ded2b7c1e31 100644 > > > > > --- a/drivers/infiniband/hw/mlx5/dm.c > > > > > +++ b/drivers/infiniband/hw/mlx5/dm.c > > > > > @@ -282,7 +282,7 @@ static struct ib_dm *handle_alloc_dm_memic(struct ib_ucontext *ctx, > > > > > int err; > > > > > u64 address; > > > > > > > > > > - if (!MLX5_CAP_DEV_MEM(dm_db->dev, memic)) > > > > > + if (!dm_db || !MLX5_CAP_DEV_MEM(dm_db->dev, memic)) > > > > > return ERR_PTR(-EOPNOTSUPP); > > > > > > > > nit: -EOPNOTSUPP doesn't feel like the right error code > > > > in the !dm_db case. > > > > > > Why? This error is returned to the user through mlx5_ib_alloc_dm(). > > > > Because, as I understand things, such a case would be due to a memory > > allocation failure, not by the device not supporting a feature. > > > > handle_alloc_dm_memic() already returns ERR_PTR(-ENOMEM) if kzalloc() fails. > > I'd suggest doing so for the !dm_db case too. > > !dm_db case can be because of missing capabilities and EOPNOTSUPP is a > way to inform users about it. Understood. No further objections from my side. ...