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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 7 May 2020 01:57:33 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Sriram Chadalavada <sriram.chadalavada@...dleap.ca>
Cc:     netdev@...r.kernel.org
Subject: Re: Kernel crash in DSA/Marvell 6176 switch in 5.4.36

On Wed, May 06, 2020 at 07:35:50PM -0400, Sriram Chadalavada wrote:
> For this device tree with new binding, there was no crash with 4.19.16
> kernel on an NXP imx6 device but there is with 5.4.36.
>          eth0: igb0 {
>                          compatible = "intel,igb";
>                         /* SC: New binding for the Marvell 6176 switch
> attached to the Intel Gigabit Ethernet Controller via SERDES link */
>                           mdio1: mdio@0 {
>                               #address-cells = <2>;
>                               #size-cells = <0>;
>                               status = "okay";
>                               switch0: switch0@0 {
> 
>                                 compatible = "marvell,mv88e6085";
>                                 reg = <0 0>;
>                                 interrupt-parent = <&gpio2>;
>                                 interrupts = <31 IRQ_TYPE_LEVEL_LOW>;
>                                 dsa,member = <0 0>;
>                                 mdio2: mdio@1{
>                                  ports
>                                  {

Err, what? This would never work for 4.19.16, or any kernel version.

     Andrew

Powered by blists - more mailing lists