netdev - Re: [PATCH net] dsa: mv88e6xxx: 6161: Use chip wide MAX MTU

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: <YIwNzKZbiuLZRnoR@lunn.ch>
Date:   Fri, 30 Apr 2021 16:01:48 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     David Miller <davem@...emloft.net>
Cc:     曹煜 <cao88yu@...il.com>,
        netdev <netdev@...r.kernel.org>,
        Chris Packham <chris.packham@...iedtelesis.co.nz>,
        Vivien Didelot <vivien.didelot@...il.com>
Subject: Re: [PATCH net] dsa: mv88e6xxx: 6161: Use chip wide MAX MTU

On Tue, Apr 27, 2021 at 01:34:41AM +0200, Andrew Lunn wrote:
> The datasheets suggests the 6161 uses a per port setting for jumbo
> frames. Testing has however shown this is not correct, it uses the old
> style chip wide MTU control. Change the ops in the 6161 structure to
> reflect this.
> 
> Fixes: 1baf0fac10fb ("net: dsa: mv88e6xxx: Use chip-wide max frame size for MTU")
> Reported by: 曹煜 <cao88yu@...il.com>
> Signed-off-by: Andrew Lunn <andrew@...n.ch>

self NACK.

We dug deeper and found a different real problem. Patches to follow.

   Andrew