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] [day] [month] [year] [list]
Message-ID: <02be01d9aa37$bbe042a0$33a0c7e0$@trustnetic.com>
Date: Thu, 29 Jun 2023 11:13:53 +0800
From: Jiawen Wu <jiawenwu@...stnetic.com>
To: "'Andrew Lunn'" <andrew@...n.ch>
Cc: <netdev@...r.kernel.org>,
	<mengyuanlou@...-swift.com>
Subject: RE: [PATCH net v2] net: txgbe: change LAN reset mode

On Wednesday, June 28, 2023 10:44 PM, Andrew Lunn wrote:
> On Wed, Jun 28, 2023 at 11:42:04AM +0800, Jiawen Wu wrote:
> > The old way to do LAN reset is sending reset command to firmware. Once
> > firmware performs reset, it reconfigures what it needs.
> >
> > In the new firmware versions, veto bit is introduced for NCSI/LLDP to
> > block PHY domain in LAN reset. At this point, writing register of LAN
> > reset directly makes the same effect as the old way. And it does not
> > reset MNG domain, so that veto bit does not change.
> >
> > And this change is compatible with old firmware versions, since veto
> > bit was never used.
> 
> You are posting this for net, so i assume you want this back ported.
> What is the real user observed problem here?
> 
> https://www.kernel.org/doc/Documentation/process/stable-kernel-rules.rst

No real problems have occurred so far.  Maybe it should be post to net-next.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ