From: Jakub Kicinski <kuba@kernel.org>
To: "Maciej Żenczykowski" <maze@google.com>
Cc: "Maciej Żenczykowski" <zenczykowski@gmail.com>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"Thomas Haller" <thaller@redhat.com>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"David Ahern" <dsahern@kernel.org>,
"Jiri Pirko" <jiri@resnulli.us>, "Xiao Ma" <xiaom@google.com>
Subject: Re: [PATCH net v2] ipv6 addrconf: fix bug where deleting a mngtmpaddr can create a new temporary address
Date: Thu, 20 Jul 2023 09:34:23 -0700 [thread overview]
Message-ID: <20230720093423.5fe02118@kernel.org> (raw)
In-Reply-To: <20230720160022.1887942-1-maze@google.com>
On Thu, 20 Jul 2023 09:00:22 -0700 Maciej Żenczykowski wrote:
> currently on 6.4 net/main:
>
> # ip link add dummy1 type dummy
> # echo 1 > /proc/sys/net/ipv6/conf/dummy1/use_tempaddr
> # ip link set dummy1 up
> # ip -6 addr add 2000::1/64 mngtmpaddr dev dummy1
> # ip -6 addr show dev dummy1
FTR resending the patch as part of the same thread is really counter
productive for the maintainers. We review patches in order, no MUA
I know can be told to order things correctly when new versions are sent
in reply.
Don't try too hard, be normal, please.
next prev parent reply other threads:[~2023-07-20 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 13:55 [PATCH net] ipv6 addrconf: fix bug where deleting a mngtmpaddr can create a new temporary address Maciej Żenczykowski
2023-07-12 13:58 ` Maciej Żenczykowski
2023-07-13 14:59 ` David Ahern
2023-07-13 15:03 ` Maciej Żenczykowski
2023-07-14 14:49 ` David Ahern
2023-07-18 23:08 ` Jakub Kicinski
2023-07-18 23:18 ` David Ahern
2023-07-19 6:47 ` Jiri Pirko
2023-07-19 12:50 ` Maciej Żenczykowski
2023-07-20 15:35 ` David Ahern
2023-07-20 16:00 ` [PATCH net v2] " Maciej Żenczykowski
2023-07-20 16:34 ` Jakub Kicinski [this message]
2023-07-20 16:52 ` Maciej Żenczykowski
2023-07-24 12:07 ` Maciej Żenczykowski
2023-07-24 18:09 ` Jakub Kicinski
2023-07-24 18:20 ` Maciej Żenczykowski
2023-07-24 18:26 ` David Ahern
2023-07-24 23:00 ` patchwork-bot+netdevbpf
2023-07-25 4:59 ` Maciej Żenczykowski
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=20230720093423.5fe02118@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thaller@redhat.com \
--cc=xiaom@google.com \
--cc=zenczykowski@gmail.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 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.