netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Di Zhu <zhudi21@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, maheshb@google.com,
	netdev@vger.kernel.org, rose.chen@huawei.com
Subject: Re: [PATCH] ipvlan: Add handling of NETDEV_UP events
Date: Thu, 29 Jul 2021 21:20:05 +0000	[thread overview]
Message-ID: <162759360578.14384.13077245399190990156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210729131930.1991-1-zhudi21@huawei.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Thu, 29 Jul 2021 21:19:30 +0800 you wrote:
> When an ipvlan device is created on a bond device, the link state
> of the ipvlan device may be abnormal. This is because bonding device
> allows to add physical network card device in the down state and so
> NETDEV_CHANGE event will not be notified to other listeners, so ipvlan
> has no chance to update its link status.
> 
> The following steps can cause such problems:
> 	1) bond0 is down
> 	2) ip link add link bond0 name ipvlan type ipvlan mode l2
> 	3) echo +enp2s7 >/sys/class/net/bond0/bonding/slaves
> 	4) ip link set bond0 up
> 
> [...]

Here is the summary with links:
  - ipvlan: Add handling of NETDEV_UP events
    https://git.kernel.org/netdev/net-next/c/57fb346cc7d0

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



      reply	other threads:[~2021-07-29 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 13:19 [PATCH] ipvlan: Add handling of NETDEV_UP events Di Zhu
2021-07-29 21:20 ` 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=162759360578.14384.13077245399190990156.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=maheshb@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=rose.chen@huawei.com \
    --cc=zhudi21@huawei.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).