From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
gal@nvidia.com, kees@kernel.org, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, michaelgur@nvidia.com, moshe@nvidia.com,
saeedm@nvidia.com, shayd@nvidia.com
Subject: Re: [PATCH net] net/mlx5: fw_tracer, return NULL on create error
Date: Sat, 01 Aug 2026 01:40:08 +0000 [thread overview]
Message-ID: <178554840864.979996.15714749578017407397.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260729080402.2427184-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Jul 2026 11:04:02 +0300 you wrote:
> From: Michael Guralnik <michaelgur@nvidia.com>
>
> Tracer creation can fail by returning either NULL or ERR_PTR.
> The return value is stored without a check on the device, and users
> treat ERR_PTR and NULL the same way.
> This also causes a crash in the core dump logic, which is missing the
> ERR_PTR check and ends up dereferencing it, as shown in the trace below.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: fw_tracer, return NULL on create error
https://git.kernel.org/netdev/net/c/af39eb111ce6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-01 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 8:04 [PATCH net] net/mlx5: fw_tracer, return NULL on create error Tariq Toukan
2026-08-01 1:40 ` patchwork-bot+netdevbpf [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=178554840864.979996.15714749578017407397.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=michaelgur@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shayd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.