From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Andy Ren <andy.ren@getcruise.com>, netdev@vger.kernel.org
Cc: richardbgobert@gmail.com, davem@davemloft.net,
wsa+renesas@sang-engineering.com, edumazet@google.com,
petrm@nvidia.com, kuba@kernel.org, pabeni@redhat.com,
corbet@lwn.net, andrew@lunn.ch, dsahern@gmail.com,
sthemmin@microsoft.com, idosch@idosch.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
roman.gushchin@linux.dev
Subject: Re: [PATCH net-next] net/core: Allow live renaming when an interface is up
Date: Fri, 4 Nov 2022 08:56:46 +0700 [thread overview]
Message-ID: <b680a914-ad3c-4167-1108-2e2db633609b@gmail.com> (raw)
In-Reply-To: <20221103235847.3919772-1-andy.ren@getcruise.com>
On 11/4/22 06:58, Andy Ren wrote:
> This patch allows a network interface to be renamed when the interface
> is up.
>
> Live renaming was added as a failover in the past, and there has been no
> arising issues of user space breaking. Furthermore, it seems that this
> flag was added because in the past, IOCTL was used for renaming, which
> would not notify the user space. Nowadays, it appears that the user
> space receives notifications regardless of the state of the network
> device (e.g. rtnetlink_event()). The listeners for NETDEV_CHANGENAME
> also do not strictly ensure that the netdev is up or not.
>
> Hence, this patch seeks to remove the live renaming flag and checks due
> to the aforementioned reasons.
>
> The changes are of following:
> - Remove IFF_LIVE_RENAME_OK flag declarations
> - Remove check in dev_change_name that checks whether device is up and
> if IFF_LIVE_RENAME_OK is set by the network device's priv_flags
> - Remove references of IFF_LIVE_RENAME_OK in the failover module
>
You have sent the patch twice, yet with same content ([1] and [2]),
so I reply to this latter version instead.
Please write the patch description in imperative mood ("make foo do
bar") instead of descriptive one like you have written ("this patch/commit
makes foo do bar").
Thanks.
[1]: https://lore.kernel.org/linux-doc/20221103224644.3806447-1-andy.ren@getcruise.com/
[2]: https://lore.kernel.org/linux-doc/20221103235847.3919772-1-andy.ren@getcruise.com/
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-11-04 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 23:58 Andy Ren
2022-11-04 1:56 ` Bagas Sanjaya [this message]
2022-11-04 2:19 ` Stephen Hemminger
2022-11-04 2:50 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2022-11-03 22:46 Andy Ren
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=b680a914-ad3c-4167-1108-2e2db633609b@gmail.com \
--to=bagasdotme@gmail.com \
--cc=andrew@lunn.ch \
--cc=andy.ren@getcruise.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=richardbgobert@gmail.com \
--cc=roman.gushchin@linux.dev \
--cc=sthemmin@microsoft.com \
--cc=wsa+renesas@sang-engineering.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®