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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/