From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, ecree.xilinx@gmail.com,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com,
simon.horman@corigine.com
Subject: Re: [PATCH net-next] sfc: fix use-after-free in efx_tc_flower_record_encap_match()
Date: Sat, 13 May 2023 20:00:20 +0000 [thread overview]
Message-ID: <168400802036.779.18008463088768762971.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230512153558.15025-1-edward.cree@amd.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 12 May 2023 16:35:58 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> When writing error messages to extack for pseudo collisions, we can't
> use encap->type as encap has already been freed. Fortunately the
> same value is stored in local variable em_type, so use that instead.
>
> Fixes: 3c9561c0a5b9 ("sfc: support TC decap rules matching on enc_ip_tos")
> Reported-by: Simon Horman <simon.horman@corigine.com>
> Signed-off-by: Edward Cree <ecree.xilinx@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next] sfc: fix use-after-free in efx_tc_flower_record_encap_match()
https://git.kernel.org/netdev/net-next/c/befcc1fce564
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:[~2023-05-13 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 15:35 [PATCH net-next] sfc: fix use-after-free in efx_tc_flower_record_encap_match() edward.cree
2023-05-12 15:56 ` Simon Horman
2023-05-13 20:00 ` 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=168400802036.779.18008463088768762971.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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.