aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/drivers/net/hyperv
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2024-01-29 14:03:08 +0100
committerJakub Kicinski <kuba@kernel.org>2024-02-01 08:29:36 -0800
commit7b55984c96ffe9e236eb9c82a2196e0b1f84990d (patch)
treea357b45b471e3c26730d8f73f56b62f3768eb43c /drivers/net/hyperv
parentnet: sysfs: Fix /sys/class/net/<iface> path (diff)
downloadwireguard-linux-7b55984c96ffe9e236eb9c82a2196e0b1f84990d.tar.xz
wireguard-linux-7b55984c96ffe9e236eb9c82a2196e0b1f84990d.zip
xen-netback: properly sync TX responses
Invoking the make_tx_response() / push_tx_responses() pair with no lock held would be acceptable only if all such invocations happened from the same context (NAPI instance or dealloc thread). Since this isn't the case, and since the interface "spec" also doesn't demand that multicast operations may only be performed with no in-flight transmits, MCAST_{ADD,DEL} processing also needs to acquire the response lock around the invocations. To prevent similar mistakes going forward, "downgrade" the present functions to private helpers of just the two remaining ones using them directly, with no forward declarations anymore. This involves renaming what so far was make_tx_response(), for the new function of that name to serve the new (wrapper) purpose. While there, - constify the txp parameters, - correct xenvif_idx_release()'s status parameter's type, - rename {,_}make_tx_response()'s status parameters for consistency with xenvif_idx_release()'s. Fixes: 210c34dcd8d9 ("xen-netback: add support for multicast control") Cc: stable@vger.kernel.org Signed-off-by: Jan Beulich <jbeulich@suse.com> Reviewed-by: Paul Durrant <paul@xen.org> Link: https://lore.kernel.org/r/980c6c3d-e10e-4459-8565-e8fbde122f00@suse.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/hyperv')
0 files changed, 0 insertions, 0 deletions