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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 7 Jan 2020 10:06:07 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Stefan Wahren <stefan.wahren@...e.com>,
        Eric Dumazet <eric.dumazet@...il.com>,
        RENARD Pierre-Francois <pfrenard@...il.com>,
        nsaenzjulienne@...e.de, woojung.huh@...rochip.com,
        UNGLinuxDriver@...rochip.com, netdev@...r.kernel.org,
        linux-usb@...r.kernel.org
Subject: Re: [RPI 3B+ / TSO / lan78xx ]



On 1/7/20 9:30 AM, Stefan Wahren wrote:
> Hi Eric,
> 
> Am 07.01.20 um 18:04 schrieb Eric Dumazet:
>>

>>
>> I doubt TSO and SACK have a serious generic bug like that.
>>
>> Most likely the TSO implementation on the driver/NIC has a bug .
> 
> Yes, the issue isn't reproducible with the Raspberry Pi 3B and the same
> kernel (without +). The main difference between both boards is the
> different ethernet USB chip:
> 
> Raspberry Pi 3B: smsc95xx
> Raspberry Pi 3B+: lan78xx
> 
>>
>> Anyway you do not provide a kernel version, I am not sure what you expect from us.
> 
> It's Linux 5.4.7 (arm64) as in the provided github link. I asked
> Pierre-Francois to report this issue here, so the issue get addressed
> properly. Currently this very old bug not fixed in mainline and the
> Raspberry Pi vendor tree uses a workaround (disable TSO).

This is puzzling.

Bug seems trivial enough :/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ