Re: [PATCH net] xen-netback: properly sync TX responses

2024-02-01 Thread patchwork-bot+netdevbpf
Hello: This patch was applied to netdev/net.git (main) by Jakub Kicinski : On Mon, 29 Jan 2024 14:03:08 +0100 you wrote: > 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

Re: [PATCH net] xen-netback: properly sync TX responses

2024-02-01 Thread Paul Durrant
On 29/01/2024 13:03, Jan Beulich wrote: 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

Re: [PATCH net] xen-netback: properly sync TX responses

2024-02-01 Thread Paul Durrant
On 01/02/2024 00:23, Jakub Kicinski wrote: On Mon, 29 Jan 2024 14:03:08 +0100 Jan Beulich wrote: 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

Re: [PATCH net] xen-netback: properly sync TX responses

2024-01-31 Thread Jakub Kicinski
On Mon, 29 Jan 2024 14:03:08 +0100 Jan Beulich wrote: > 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

[PATCH net] xen-netback: properly sync TX responses

2024-01-29 Thread Jan Beulich
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