All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	luca.czesla@mail.schwarz, felix.huettner@mail.schwarz,
	dev@openvswitch.org, linux-kernel@vger.kernel.org,
	pshelar@ovn.org, f.weber@proxmox.com
Subject: Re: [PATCH net] openvswitch: fix lockup on tx to unregistering netdev with carrier
Date: Sat, 11 Jan 2025 02:40:32 +0000	[thread overview]
Message-ID: <173656323206.2272951.314255670629847295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250109122225.4034688-1-i.maximets@ovn.org>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  9 Jan 2025 13:21:24 +0100 you wrote:
> Commit in a fixes tag attempted to fix the issue in the following
> sequence of calls:
> 
>     do_output
>     -> ovs_vport_send
>        -> dev_queue_xmit
>           -> __dev_queue_xmit
>              -> netdev_core_pick_tx
>                 -> skb_tx_hash
> 
> [...]

Here is the summary with links:
  - [net] openvswitch: fix lockup on tx to unregistering netdev with carrier
    https://git.kernel.org/netdev/net/c/47e55e4b410f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-01-11  2:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 12:21 [PATCH net] openvswitch: fix lockup on tx to unregistering netdev with carrier Ilya Maximets
2025-01-09 16:13 ` Friedrich Weber
2025-01-09 17:05 ` [ovs-dev] " Aaron Conole
2025-01-10 11:50   ` Friedrich Weber
2025-01-11  2:40 ` 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=173656323206.2272951.314255670629847295.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=edumazet@google.com \
    --cc=f.weber@proxmox.com \
    --cc=felix.huettner@mail.schwarz \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.czesla@mail.schwarz \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pshelar@ovn.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.