From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 5.4 v3 2/2] openvswitch: fix lockup on tx to unregistering netdev with carrier
Date: Wed, 26 Mar 2025 13:54:45 -0400 [thread overview]
Message-ID: <20250326134447-694c54839fb6d79b@stable.kernel.org> (raw)
In-Reply-To: <20250326155800.4133904-3-florian.fainelli@broadcom.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 47e55e4b410f7d552e43011baa5be1aab4093990
WARNING: Author mismatch between patch and upstream commit:
Backport author: Florian Fainelli<florian.fainelli@broadcom.com>
Commit author: Ilya Maximets<i.maximets@ovn.org>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 82f433e8dd06)
6.6.y | Present (different SHA1: ea966b669878)
6.1.y | Present (different SHA1: ea9e990356b7)
5.15.y | Not found
5.10.y | Not found
Note: The patch differs from the upstream commit:
---
1: 47e55e4b410f7 ! 1: 6bcba442a60ff openvswitch: fix lockup on tx to unregistering netdev with carrier
@@ Metadata
## Commit message ##
openvswitch: fix lockup on tx to unregistering netdev with carrier
+ [ Upstream commit 47e55e4b410f7d552e43011baa5be1aab4093990 ]
+
Commit in a fixes tag attempted to fix the issue in the following
sequence of calls:
@@ Commit message
Reviewed-by: Aaron Conole <aconole@redhat.com>
Link: https://patch.msgid.link/20250109122225.4034688-1-i.maximets@ovn.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+ Signed-off-by: Sasha Levin <sashal@kernel.org>
+ Signed-off-by: Carlos Soto <carlos.soto@broadcom.com>
+ Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
## net/openvswitch/actions.c ##
@@ net/openvswitch/actions.c: static void do_output(struct datapath *dp, struct sk_buff *skb, int out_port,
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2025-03-26 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 15:57 [PATCH stable 5.4 v3 0/2] openvswitch port output fixes Florian Fainelli
2025-03-26 15:57 ` [PATCH stable 5.4 v3 1/2] net: openvswitch: fix race on port output Florian Fainelli
2025-03-26 17:54 ` Sasha Levin
2025-03-26 15:58 ` [PATCH stable 5.4 v3 2/2] openvswitch: fix lockup on tx to unregistering netdev with carrier Florian Fainelli
2025-03-26 17:54 ` Sasha Levin [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=20250326134447-694c54839fb6d79b@stable.kernel.org \
--to=sashal@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=stable@vger.kernel.org \
/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.