| Message ID | 20261103100534.1310071-1-vulab@iscas.ac.cn |
|---|---|
| State | New |
| Headers | show |
| Series | net: ixgbevf: drop the SA reference if secpath_set() fails | expand |
On Tue, 03 Nov 2026 10:05:34 +0000, Wentao Liang wrote: > ixgbevf_ipsec_rx() takes a reference on the xfrm_state returned by > ixgbevf_ipsec_find_rx_state(). On success that reference is handed over > to the skb's security path, which releases it when the skb is freed. > When secpath_set() cannot allocate the extension it returns NULL, but > the function returns without releasing the xfrm_state, so the SA > reference is leaked. > > Put the reference before bailing out. > > Fixes: 0062e7cc955e ("ixgbevf: add VF IPsec offload code") > Cc: stable@vger.kernel.org > Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex > Signed-off-by: Wentao Liang <vulab@iscas.ac.cn> > --- > drivers/net/ethernet/intel/ixgbevf/ipsec.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > Multiple things here: 1. Your team ignored completely previous feedback. Multiple times. 2. You use multiple identities with this email address, thus I doubt that we speak with an actual person. 3. Your bot does not even bother running checkpatch, right? 4. Nothing of this was reproduced nor tested. 5. Finally, the same feedback: You sent multiple independent patches, to multiple independent subsystems. The amount of these patches clearly suggest this was AI generated and most likely not tested. More importantly, you sent all this work without properly organizing relevant patches into patchsets. This makes reviewing difficult and might cause multiple reviewers to address the same issue. Replying to the entire set is impossible and requires handling each patch independently, instead of applying or discarding the set. Maintainers also won't see the bigger picture of your work. Quite worrying. This is on the verge of hostile patch: bomb us with so many contributions, we won't be able to handle them in efficient manner, like responding ONCE to ask you to slow down. Considering all this is untested and LLM generated, I have even more doubts whether this should be considered for review. Please read kernel documentation BEFORE posting more work. It will explain you how to identify subsystems, how to organize your work per subsystem (so a patchset grouping multiple patches with a short cover letter), how to document the issue discovery method and what was or was not tested. Best regards, Krzysztof
diff --git a/drivers/net/ethernet/intel/ixgbevf/ipsec.c b/drivers/net/ethernet/intel/ixgbevf/ipsec.c index 076fd0a24858..bf3fcab3bd57 100644 --- a/drivers/net/ethernet/intel/ixgbevf/ipsec.c +++ b/drivers/net/ethernet/intel/ixgbevf/ipsec.c @@ -596,8 +596,10 @@ void ixgbevf_ipsec_rx(struct ixgbevf_ring *rx_ring, return; sp = secpath_set(skb); - if (unlikely(!sp)) + if (unlikely(!sp)) { + xfrm_state_put(xs); return; + } sp->xvec[sp->len++] = xs; sp->olen++;
ixgbevf_ipsec_rx() takes a reference on the xfrm_state returned by ixgbevf_ipsec_find_rx_state(). On success that reference is handed over to the skb's security path, which releases it when the skb is freed. When secpath_set() cannot allocate the extension it returns NULL, but the function returns without releasing the xfrm_state, so the SA reference is leaked. Put the reference before bailing out. Fixes: 0062e7cc955e ("ixgbevf: add VF IPsec offload code") Cc: stable@vger.kernel.org Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex Signed-off-by: Wentao Liang <vulab@iscas.ac.cn> --- drivers/net/ethernet/intel/ixgbevf/ipsec.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)