netdev - RE: [PATCH] r8169: more driver shutdown WoL regression.

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]

Date:	Fri, 11 Nov 2011 16:37:20 +0800
From:	hayeswang <hayeswang@...ltek.com>
To:	'Francois Romieu' <romieu@...zoreil.com>
CC:	<netdev@...r.kernel.org>, 'Stefan Becker' <chemobejk@...il.com>,
	'David Miller' <davem@...emloft.net>,
	'Ben Hutchings' <bhutchings@...arflare.com>
Subject: RE: [PATCH] r8169: more driver shutdown WoL regression.

Francois Romieu [mailto:romieu@...zoreil.com] 
[...]
> 
> Hayes, should I consider similar cross-behaviors between 
> RxConfig and WoL
> ConfigX bits with different configurations ?
> 
> I.e., assuming Config5.UWF is active and Config3.MagicPacket 
> is not, can
> RxConfig.AcceptMyPhys make a difference to the WoL function ?
> 

Yes. The RxConfig influences if you could receive unicast, multicast, or
broadcast packets. If you don't enable the relative bits of RxConfig, the WOL
feature won't  work no matter which WOL mode you set.

> > Further, it may be dangerous to enable both rx_enable 
> (ChipCmd bit 3) and
> > RxConfig for 8168b for WOL, because the hw would try to 
> write the rx buffer.
> 
> Ok.
> 
 
Best Regards,
Hayes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html