From: Stephen Hemminger <stephen@networkplumber.org>
To: Chuck Lever <cel@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
BMT@zurich.ibm.com, tom@talpey.com
Subject: Re: [PATCH RFC 1/3] net/tun: Ensure tun devices have a MAC address
Date: Fri, 5 May 2023 09:59:32 -0700 [thread overview]
Message-ID: <20230505095932.4025d469@hermes.local> (raw)
In-Reply-To: <168330132769.5953.7109360341846745035.stgit@oracle-102.nfsv4bat.org>
On Fri, 05 May 2023 11:42:17 -0400
Chuck Lever <cel@kernel.org> wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> A non-zero MAC address enables a network device to be assigned as
> the underlying device for a virtual RDMA device. Without a non-
> zero MAC address, cma_acquire_dev_by_src_ip() is unable to find the
> underlying egress device that corresponds to a source IP address,
> and rdma_resolve_address() fails.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> drivers/net/tun.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index d4d0a41a905a..da85abfcd254 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -1384,7 +1384,7 @@ static void tun_net_initialize(struct net_device *dev)
>
> /* Point-to-Point TUN Device */
> dev->hard_header_len = 0;
> - dev->addr_len = 0;
> + dev->addr_len = ETH_ALEN;
> dev->mtu = 1500;
>
> /* Zero header length */
This is a bad idea.
TUN devices are L3 devices without any MAC address.
This patch will change the semantics and break users.
If you want an L2 address, you need to use TAP, not TUN device.
next prev parent reply other threads:[~2023-05-05 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 15:41 [PATCH RFC 0/3] siw on tunnel devices Chuck Lever
2023-05-05 15:42 ` [PATCH RFC 1/3] net/tun: Ensure tun devices have a MAC address Chuck Lever
2023-05-05 16:59 ` Stephen Hemminger [this message]
2023-05-05 17:09 ` Chuck Lever III
2023-05-05 15:42 ` [PATCH RFC 2/3] net/lo: Ensure lo " Chuck Lever
2023-05-05 16:57 ` Stephen Hemminger
2023-05-05 15:43 ` [PATCH RFC 3/3] RDMA/siw: Require non-zero 6-byte MACs for soft iWARP Chuck Lever
2023-05-05 19:58 ` Jason Gunthorpe
2023-05-05 20:03 ` Chuck Lever III
2023-05-06 18:05 ` Chuck Lever III
2023-05-23 19:18 ` Chuck Lever III
2023-05-23 19:44 ` Tom Talpey
2023-05-23 22:50 ` Chuck Lever III
2023-05-31 19:04 ` Jason Gunthorpe
2023-05-31 19:11 ` Chuck Lever III
2023-05-31 20:09 ` Jason Gunthorpe
2023-05-31 20:19 ` Chuck Lever III
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=20230505095932.4025d469@hermes.local \
--to=stephen@networkplumber.org \
--cc=BMT@zurich.ibm.com \
--cc=cel@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom@talpey.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).