From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753500AbdDJNPs (ORCPT ); Mon, 10 Apr 2017 09:15:48 -0400 Received: from vps0.lunn.ch ([178.209.37.122]:53657 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752877AbdDJNPk (ORCPT ); Mon, 10 Apr 2017 09:15:40 -0400 Date: Mon, 10 Apr 2017 15:15:33 +0200 From: Andrew Lunn To: Juergen Borleis Cc: kernel@pengutronix.de, f.fainelli@gmail.com, vivien.didelot@savoirfairelinux.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, davem@davemloft.net Subject: Re: [PATCH v2 1/4] net: dsa: add support for the SMSC-LAN9303 tagging format Message-ID: <20170410131533.GA19820@lunn.ch> References: <20170407081502.30172-1-jbe@pengutronix.de> <20170407081502.30172-2-jbe@pengutronix.de> <20170407130610.GD17290@lunn.ch> <201704100918.03272.jbe@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201704100918.03272.jbe@pengutronix.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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