linux-kernel - Re: [PATCH] net: arp, ipv6: handle special case of tap device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20181002.222540.1948082296309410659.davem@davemloft.net>
Date:   Tue, 02 Oct 2018 22:25:40 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     vdronov@...hat.com
Cc:     kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
        netdev@...r.kernel.org, syzkaller@...glegroups.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: arp, ipv6: handle special case of tap device

From: Vladis Dronov <vdronov@...hat.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?