netdev - Re: Net: [DSA]: dsa-loop kernel panic

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: <dd42f431-d555-fcd2-b25e-50aeecbb513b@gmail.com>
Date:   Thu, 30 Apr 2020 10:12:34 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Allen <allen.pais@...cle.com>, netdev@...r.kernel.org,
        Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>
Subject: Re: Net: [DSA]: dsa-loop kernel panic

On 4/29/20 11:24 PM, Allen wrote:
> Hi,
> 
>   We ran into a kernel panic with dsa-loop.
> Here are the details:
> 
> VM: aarch64 kvm running 5.7.0-rc3+
> 
> $ modprobe dsa-loop
> [   25.968427] dsa-loop fixed-0:1f: DSA mockup driver: 0x1f
> [   25.978156] libphy: dsa slave smi: probed
> [   25.979230] dsa-loop fixed-0:1f: nonfatal error -95 setting MTU on
> port 0
> [   25.980974] dsa-loop fixed-0:1f lan1 (uninitialized): PHY
> [dsa-0.0:00] driver [Generic PHY] (irq=POLL)
> [   25.983855] dsa-loop fixed-0:1f: nonfatal error -95 setting MTU on
> port 1
> [   25.985523] dsa-loop fixed-0:1f lan2 (uninitialized): PHY
> [dsa-0.0:01] driver [Generic PHY] (irq=POLL)
> [   25.988127] dsa-loop fixed-0:1f: nonfatal error -95 setting MTU on
> port 2
> [   25.989775] dsa-loop fixed-0:1f lan3 (uninitialized): PHY
> [dsa-0.0:02] driver [Generic PHY] (irq=POLL)
> [   25.992651] dsa-loop fixed-0:1f: nonfatal error -95 setting MTU on
> port 3
> [   25.994472] dsa-loop fixed-0:1f lan4 (uninitialized): PHY
> [dsa-0.0:03] driver [Generic PHY] (irq=POLL)
> [   25.997015] DSA: tree 0 setup
> [root@...alhost ~]# [   26.002672] dsa-loop fixed-0:1f lan1: configuring
> for phy/gmii link mode
> [   26.008264] dsa-loop fixed-0:1f lan1: Link is Up - 100Mbps/Full -
> flow control off
> [   26.010098] IPv6: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
> [   26.014539] dsa-loop fixed-0:1f lan3: configuring for phy/gmii link mode
> [   26.021323] dsa-loop fixed-0:1f lan2: configuring for phy/gmii link mode
> [   26.023274] dsa-loop fixed-0:1f lan3: Link is Up - 100Mbps/Full -
> flow control off
> [   26.028358] dsa-loop fixed-0:1f lan4: configuring for phy/gmii link mode
> [   26.036157] dsa-loop fixed-0:1f lan2: Link is Up - 100Mbps/Full -
> flow control off
> [   26.037875] dsa-loop fixed-0:1f lan4: Link is Up - 100Mbps/Full -
> flow control off
> [   26.039858] IPv6: ADDRCONF(NETDEV_CHANGE): lan3: link becomes ready
> [   26.041527] IPv6: ADDRCONF(NETDEV_CHANGE): lan2: link becomes ready
> [   26.043219] IPv6: ADDRCONF(NETDEV_CHANGE): lan4: link becomes ready

you have missed an important detail here which is the master device that
was used for DSA. The current code defaults to whatever "eth0" is, what
does this map to for your configuration?
-- 
Florian