On 10/14/2012 07:19 PM, Dmitry Fleytman wrote: > There is a race condition in e1000 driver. > It enables HW receive before RX rings initalization. > In case of specific timing this may lead to host memory corruption > due to DMA write to arbitrary memory location. > Following patch fixes this issue by reordering initialization steps. > > Other Intel network drivers does not seem to have this issue. > > Dmitry Fleytman (1): > RX initialization sequence fixed - enable RX after corresponding ring > initialization only > > drivers/net/ethernet/intel/e1000/e1000_ethtool.c | 9 +++++---- > drivers/net/ethernet/intel/e1000/e1000_main.c | 18 ++++++++++++++++-- > 2 files changed, 21 insertions(+), 6 deletions(-) >
Would it be at all possible to copy netdev on networking-related discussions? ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
