From: Jakub Kicinski <kuba@kernel.org>
To: Venkat Venkatsubra <venkat.x.venkatsubra@oracle.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, maheshb@google.com,
edumazet@google.com, gia-khanh.nguyen@oracle.com
Subject: Re: [PATCH net-next] Add handling of NETDEV_DOWN event
Date: Wed, 3 Apr 2024 19:07:10 -0700 [thread overview]
Message-ID: <20240403190704.6df9481d@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <1711892489-27931-1-git-send-email-venkat.x.venkatsubra@oracle.com>
On Sun, 31 Mar 2024 06:41:28 -0700 Venkat Venkatsubra wrote:
> When ethP is the parent interface of ipvlan interface ethC,
> and you do
>
> # ip link set ethP down
>
> ethC's link state is not brought down.
>
> In the below example, ens5 is the host interface which is the
> parent of the ipvlan interface eth0 in the container.
>
> Host:
>
> [root@gkn-podman-x64 ~]# ip link set ens5 down
> [root@gkn-podman-x64 ~]# ip -d link show dev ens5
> 3: ens5: <BROADCAST,MULTICAST> mtu 9000 qdisc mq state DOWN
> ...
> [root@gkn-podman-x64 ~]#
>
> Container:
>
> [root@testnode-ol8 /]# ip -d link show dev eth0
> 2: eth0@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 state UNKNOWN
> ...
> ipvlan mode l2 bridge
> [root@testnode-ol8 /]#
>
> eth0 continues to remain UP.
No need to add a cover letter for a single patch.
Add what's relevant to the main commit message.
prev parent reply other threads:[~2024-04-04 2:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 13:41 Venkat Venkatsubra
2024-03-31 13:41 ` [PATCH net-next] ipvlan: handle " Venkat Venkatsubra
2024-04-04 2:08 ` Jakub Kicinski
2024-04-04 2:07 ` Jakub Kicinski [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=20240403190704.6df9481d@kicinski-fedora-PC1C0HJN \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gia-khanh.nguyen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=venkat.x.venkatsubra@oracle.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
all inboxes | Powered by JetHome®