From: David Miller <davem@davemloft.net>
To: vdronov@redhat.com
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org, syzkaller@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: arp, ipv6: handle special case of tap device
Date: Tue, 02 Oct 2018 22:25:40 -0700 (PDT) [thread overview]
Message-ID: <20181002.222540.1948082296309410659.davem@davemloft.net> (raw)
In-Reply-To: <1615981257.17285278.1538393552487.JavaMail.zimbra@redhat.com>
From: Vladis Dronov <vdronov@redhat.com>
Date: Mon, 1 Oct 2018 07:32:32 -0400 (EDT)
> Probably, this functionality is already used by some userspace, so I
> believe, I cannot just remove TUNSETLINK ioctl.
Who uses it, how do they use it, and what do they sanely expect about
the link layer header properties of a tap device which has had ->type
changed?
next prev parent reply other threads:[~2018-10-03 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 9:30 [PATCH] net: arp, ipv6: handle special case of tap device Vladis Dronov
2018-09-29 18:40 ` David Miller
2018-10-01 11:32 ` Vladis Dronov
2018-10-03 5:25 ` David Miller [this message]
2018-10-03 13:25 ` Vladis Dronov
2018-10-03 16:37 ` David Miller
2018-10-04 9:53 ` Kalle Valo
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=20181002.222540.1948082296309410659.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=vdronov@redhat.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 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).