netdev - Re: [PATCH net-next] net: Enabled MPLS support for devices of type ARPHRD

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: <20200723.150025.1966416182386618182.davem@davemloft.net>
Date:   Thu, 23 Jul 2020 15:00:25 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     martinvarghesenokia@...il.com
Cc:     netdev@...r.kernel.org, kuba@...nel.org, martin.varghese@...ia.com
Subject: Re: [PATCH net-next] net: Enabled MPLS support for devices of type
 ARPHRD_NONE.

From: Martin Varghese <martinvarghesenokia@...il.com>
Date: Wed, 22 Jul 2020 21:43:21 +0530

> From: Martin Varghese <martin.varghese@...ia.com>
> 
> This change enables forwarding of MPLS packets from bareudp tunnel
> device which is of type ARPHRD_NONE.
> 
> Signed-off-by: Martin Varghese <martin.varghese@...ia.com>

This restriction looks just like a massive guessing game.

What is needed by MPLS by a device specifically, and can therefore
this restrictive test be removed entirely?