From: Leon Romanovsky <leon@kernel.org>
To: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Stav Aviram <saviram@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-rdma@vger.kernel.org, Mark Bloch <markb@mellanox.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH mlx5-next] net/mlx5: Check device memory pointer before usage
Date: Tue, 1 Jul 2025 14:30:14 +0300 [thread overview]
Message-ID: <20250701113014.GA6278@unreal> (raw)
In-Reply-To: <ecd14fd4-91b2-4bdf-af9c-cc6f555f989b@linux.intel.com>
On Mon, Jun 30, 2025 at 01:18:22PM +0200, Dawid Osuchowski wrote:
> On 2025-06-30 12:35 PM, Leon Romanovsky wrote:
> > From: Stav Aviram <saviram@nvidia.com>
> >
> > 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 <saviram@nvidia.com>
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
>
> Given this is a fix, the net tree should be targeted instead of next.
This fix is mainly for RDMA and changes in net-next are by-product. The
current target is mlx5-next.
Thanks
>
> Best regards,
> Dawid
prev parent reply other threads:[~2025-07-01 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 10:35 [PATCH mlx5-next] net/mlx5: Check device memory pointer before usage Leon Romanovsky
2025-06-30 10:56 ` Michal Swiatkowski
2025-07-01 11:33 ` Leon Romanovsky
2025-06-30 11:18 ` Dawid Osuchowski
2025-07-01 11:30 ` Leon Romanovsky [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=20250701113014.GA6278@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=dawid.osuchowski@linux.intel.com \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=saviram@nvidia.com \
--cc=tariqt@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