All of lore.kernel.org
 help / color / mirror / Atom feed
From: rocco.yue <rocco.yue@mediatek.com>
To: Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: wsd_upstream@mediatek.com, netdev@vger.kernel.org,
	"rocco.yue" <rocco.yue@mediatek.com>,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next 2/2] net: ipv6: don't generate link local address on PUREIP device
Date: Thu, 4 Feb 2021 14:06:01 +0800	[thread overview]
Message-ID: <1612418761.1817.19.camel@mbjsdccf07> (raw)
In-Reply-To: <20210129190737.78834c9d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Fri, 2021-01-29 at 19:07 -0800, Jakub Kicinski wrote:
> On Thu, 28 Jan 2021 13:58:09 +0800 Rocco Yue wrote:
> > PUREIP device such as ccmni does not need kernel to generate
> > link-local address in any addr_gen_mode, generally, it shall
> > use the IPv6 Interface Identifier, as provided by the GGSN,
> > to create its IPv6 link-ocal Unicast Address.
> > 
> > Signed-off-by: Rocco Yue <rocco.yue@mediatek.com>
> 
> There is no ccmni driver in the tree - is this for non-upstream
> driver?

ccmni is the name of MediaTek mobile interface, currently, it is
non-upstream driver and we plan to upstream these driver codes this
year.

Honestly, the reason why upstreamed this patch is not only that it can
be used by ccmni, but also I observed that the current Linux kernel does
not generate ipv6 link-local address only when addr_gen_mode ==
IN6_ADDR_GEN_MODE_NONE. We hope kernel can add a device type so that no
ipv6 link-local address can be generated in any addr_gen_mode.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: rocco.yue <rocco.yue@mediatek.com>
To: Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: wsd_upstream@mediatek.com, netdev@vger.kernel.org,
	"rocco.yue" <rocco.yue@mediatek.com>,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next 2/2] net: ipv6: don't generate link local address on PUREIP device
Date: Thu, 4 Feb 2021 14:06:01 +0800	[thread overview]
Message-ID: <1612418761.1817.19.camel@mbjsdccf07> (raw)
In-Reply-To: <20210129190737.78834c9d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Fri, 2021-01-29 at 19:07 -0800, Jakub Kicinski wrote:
> On Thu, 28 Jan 2021 13:58:09 +0800 Rocco Yue wrote:
> > PUREIP device such as ccmni does not need kernel to generate
> > link-local address in any addr_gen_mode, generally, it shall
> > use the IPv6 Interface Identifier, as provided by the GGSN,
> > to create its IPv6 link-ocal Unicast Address.
> > 
> > Signed-off-by: Rocco Yue <rocco.yue@mediatek.com>
> 
> There is no ccmni driver in the tree - is this for non-upstream
> driver?

ccmni is the name of MediaTek mobile interface, currently, it is
non-upstream driver and we plan to upstream these driver codes this
year.

Honestly, the reason why upstreamed this patch is not only that it can
be used by ccmni, but also I observed that the current Linux kernel does
not generate ipv6 link-local address only when addr_gen_mode ==
IN6_ADDR_GEN_MODE_NONE. We hope kernel can add a device type so that no
ipv6 link-local address can be generated in any addr_gen_mode.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-02-04  6:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  5:58 [PATCH net-next 2/2] net: ipv6: don't generate link local address on PUREIP device Rocco Yue
2021-01-30  3:07 ` Jakub Kicinski
2021-01-30  3:07   ` Jakub Kicinski
2021-01-30  3:07   ` Jakub Kicinski
2021-02-04  6:06   ` rocco.yue [this message]
2021-02-04  6:06     ` rocco.yue
2021-02-23  2:03     ` rocco.yue
2021-02-23  2:03       ` rocco.yue
2021-02-23  2:45       ` Jakub Kicinski
2021-02-23  2:45         ` Jakub Kicinski
2021-02-23  2:45         ` Jakub Kicinski
2021-02-23  5:40         ` rocco.yue
2021-02-23  5:40           ` rocco.yue

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=1612418761.1817.19.camel@mbjsdccf07 \
    --to=rocco.yue@mediatek.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=wsd_upstream@mediatek.com \
    --cc=yoshfuji@linux-ipv6.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.