From: Markus Elfring <Markus.Elfring@web.de>
To: Henry Martin <bsdhenrymartin@gmail.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Amir Tzin <amirtz@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>, Aya Levin <ayal@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Leon Romanovsky <leon@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH v4] net/mlx5: Fix null-ptr-deref in mlx5_create_{inner_,}ttc_table()
Date: Fri, 11 Apr 2025 16:06:16 +0200 [thread overview]
Message-ID: <1784cc08-918c-4745-bc7d-22a0217fea45@web.de> (raw)
In-Reply-To: <20250411131431.46537-2-bsdhenrymartin@gmail.com>
> Add NULL check for mlx5_get_flow_namespace() returns in
> mlx5_create_inner_ttc_table() and mlx5_create_ttc_table() to prevent
> NULL pointer dereference.
Can any other summary phrase variants become more desirable accordingly?
…
> ---
> V3 -> V4: Fix potential memory leak.
* Do you propose to complete the error handling for more function implementations?
* Please avoid duplicate source code.
* Can an other enumeration style become nicer for version numbers?
> V2 -> V3: No functional changes, just gathering the patches in a series.
Would you usually expect more than one update step then?
Regards,
Markus
next prev parent reply other threads:[~2025-04-11 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 13:14 [PATCH v4 0/1] net/mlx5: Fix null-ptr-deref in TTC table creation Henry Martin
2025-04-11 13:14 ` [PATCH v4 1/1] net/mlx5: Fix null-ptr-deref in mlx5_create_{inner_,}ttc_table() Henry Martin
2025-04-11 14:06 ` Markus Elfring [this message]
2025-04-15 8:41 ` Michal Swiatkowski
2025-04-15 11:26 ` Tariq Toukan
2025-04-11 13:45 ` [PATCH v4 0/1] net/mlx5: Fix null-ptr-deref in TTC table creation Markus Elfring
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=1784cc08-918c-4745-bc7d-22a0217fea45@web.de \
--to=markus.elfring@web.de \
--cc=amirtz@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=ayal@nvidia.com \
--cc=bsdhenrymartin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@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