From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f42.google.com ([209.85.160.42]:35455 "EHLO mail-pl0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751311AbeCESXp (ORCPT ); Mon, 5 Mar 2018 13:23:45 -0500 Received: by mail-pl0-f42.google.com with SMTP id bb3-v6so10164062plb.2 for ; Mon, 05 Mar 2018 10:23:45 -0800 (PST) Message-ID: <1520274223.109662.8.camel@gmail.com> Subject: Re: [net-next 4/4] e1000e: allocate ring descriptors with dma_zalloc_coherent From: Eric Dumazet To: Jeff Kirsher , davem@davemloft.net Cc: Pierre-Yves Kerbrat , netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com, jogreene@redhat.com, Marius Gligor Date: Mon, 05 Mar 2018 10:23:43 -0800 In-Reply-To: <20180305181631.3872-5-jeffrey.t.kirsher@intel.com> References: <20180305181631.3872-1-jeffrey.t.kirsher@intel.com> <20180305181631.3872-5-jeffrey.t.kirsher@intel.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: On Mon, 2018-03-05 at 10:16 -0800, Jeff Kirsher wrote: > From: Pierre-Yves Kerbrat > > Descriptor rings were not initialized at zero when allocated > When area contained garbage data, it caused skb_over_panic in > e1000_clean_rx_irq (if data had E1000_RXD_STAT_DD bit set) > > This patch makes use of dma_zalloc_coherent to make sure the > ring is memset at 0 to prevent the area from containing garbage. > This looks like a net candidate, fixing a bug, with 0 chance adding a regression IMO.