Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 16B48C433EF for ; Tue, 16 Nov 2021 13:40:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EC8556323D for ; Tue, 16 Nov 2021 13:40:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236803AbhKPNnJ (ORCPT ); Tue, 16 Nov 2021 08:43:09 -0500 Received: from vps0.lunn.ch ([185.16.172.187]:35906 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236566AbhKPNnH (ORCPT ); Tue, 16 Nov 2021 08:43:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=/ZTRNnUNEgr3hlsthAHSmJ8lnNXuu59AnWYQvhB9PG4=; b=ccCyq4GiHwe9oaJJZGgJwkwKyp 2GsAJntl5p5+Gvi9TMowlgtcGJIC8VpNQtKlCXKfsfDAShDZggb3MfUZcJx4qkWXqoRJECAvXH41m KrWAJ8Ph9+rBMB/lVJUb0FclkepNodv1QpU4hdarlirG2f62G5lFxD8jkzJ3kqjimWVo=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1mmygw-00DeWd-Gp; Tue, 16 Nov 2021 14:40:06 +0100 Date: Tue, 16 Nov 2021 14:40:06 +0100 From: Andrew Lunn To: Oleksij Rempel Cc: Vladimir Oltean , g@pengutronix.de, Woojung Huh , Florian Fainelli , "David S. Miller" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com, kernel@pengutronix.de, Jakub Kicinski , Vivien Didelot Subject: Re: [RFC PATCH net-next] net: dsa: microchip: implement multi-bridge support Message-ID: References: <20211108111034.2735339-1-o.rempel@pengutronix.de> <20211110123640.z5hub3nv37dypa6m@skbuf> <20211112075823.GJ12195@pengutronix.de> <20211115234546.spi7hz2fsxddn4dz@skbuf> <20211116083903.GA16121@pengutronix.de> <20211116124723.kivonrdbgqdxlryd@skbuf> <20211116131657.GC16121@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211116131657.GC16121@pengutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > What logging noise? > > I get this with current ksz driver: > [ 40.185928] br0: port 2(lan2) entered blocking state > [ 40.190924] br0: port 2(lan2) entered listening state > [ 41.043186] br0: port 2(lan2) entered blocking state > [ 55.512832] br0: port 1(lan1) entered learning state > [ 61.272802] br0: port 2(lan2) neighbor 8000.ae:1b:91:58:77:8b lost > [ 61.279192] br0: port 2(lan2) entered listening state > [ 63.113236] br0: received packet on lan1 with own address as source address (addr:00:0e:cd:00:cd:be, vlan:0) I would guess that transmission from the CPU is broken in this case. It could be looking up the destination address in the translation table and not finding an entry. So it floods the packet out all interfaces, including the CPU. So the CPU receives its own packet and gives this warning. Flooding should exclude where the frame came from. Andrew