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: <169797182424.5465.9720701078350268924.git-patchwork-notify@kernel.org>
Date:   Sun, 22 Oct 2023 10:50:24 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Doug Anderson <dianders@...omium.org>
Cc:     kuba@...nel.org, hayeswang@...ltek.com, davem@...emloft.net,
        ecgh@...omium.org, laura.nao@...labora.com,
        stern@...land.harvard.edu, horms@...nel.org,
        linux-usb@...r.kernel.org, grundler@...omium.org, bjorn@...k.no,
        edumazet@...gle.com, pabeni@...hat.com, pmalani@...omium.org,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v5 0/8] r8152: Avoid writing garbage to the adapter's
 registers

Hello:

This series was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:

On Fri, 20 Oct 2023 14:06:51 -0700 you wrote:
> This series is the result of a cooperative debug effort between
> Realtek and the ChromeOS team. On ChromeOS, we've noticed that Realtek
> Ethernet adapters can sometimes get so wedged that even a reboot of
> the host can't get them to enumerate again, assuming that the adapter
> was on a powered hub and din't lose power when the host rebooted. This
> is sometimes seen in the ChromeOS automated testing lab. The only way
> to recover adapters in this state is to manually power cycle them.
> 
> [...]

Here is the summary with links:
  - [v5,1/8] r8152: Increase USB control msg timeout to 5000ms as per spec
    https://git.kernel.org/netdev/net/c/a5feba71ec9c
  - [v5,2/8] r8152: Run the unload routine if we have errors during probe
    https://git.kernel.org/netdev/net/c/5dd176895269
  - [v5,3/8] r8152: Cancel hw_phy_work if we have an error in probe
    https://git.kernel.org/netdev/net/c/bb8adff9123e
  - [v5,4/8] r8152: Release firmware if we have an error in probe
    https://git.kernel.org/netdev/net/c/b8d35024d405
  - [v5,5/8] r8152: Check for unplug in rtl_phy_patch_request()
    https://git.kernel.org/netdev/net/c/dc90ba37a8c3
  - [v5,6/8] r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en()
    https://git.kernel.org/netdev/net/c/bc65cc42af73
  - [v5,7/8] r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE
    https://git.kernel.org/netdev/net/c/715f67f33af4
  - [v5,8/8] r8152: Block future register access if register access fails
    https://git.kernel.org/netdev/net/c/d9962b0d4202

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ