linux-kernel - Re: [PATCH v2 1/4] net: dsa: add support for the SMSC-LAN9303 tagging format

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: <20170410131533.GA19820@lunn.ch>
Date:   Mon, 10 Apr 2017 15:15:33 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Juergen Borleis <jbe@...gutronix.de>
Cc:     kernel@...gutronix.de, f.fainelli@...il.com,
        vivien.didelot@...oirfairelinux.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH v2 1/4] net: dsa: add support for the SMSC-LAN9303
 tagging format

> Hmm. In the transmit path the driver adds four bytes of explicit data after 
> the two MACs to define the outgoing port. And the hardware uses the first 
> TAG after the two MACs to forward the packet to a specific port. How should 
> a userspace app manipulate this behaviour?

Juergen

Yes, you are right. I got thinking about the Marvell driver, can it be
made to do bad things by user space, and released my own error.

There is nothing to worry about here, sorry for the noise.

     Andrew