Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp8391153ybl; Thu, 16 Jan 2020 15:57:13 -0800 (PST) X-Google-Smtp-Source: APXvYqyWL3aZx8ZD5zgauSK8UU3Ent2PqIACM7eknZw4lDo71QftgOwFBdqoCfzMWzFXOk2BSoRi X-Received: by 2002:a05:6830:1401:: with SMTP id v1mr4081061otp.360.1579219033218; Thu, 16 Jan 2020 15:57:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579219033; cv=none; d=google.com; s=arc-20160816; b=osOuMJnDA6o0D7Pk0AN7WA7J2eSzfTkclHCmGHze8vNk9TmjepPfyhjdT6HK3qGd23 w2XOmkQKm6ZilQq8/7+bzbwAWKoClTJ5/hVV/ee+pTaxQDgHZtOAyZU56bOSyagMLIM9 JY0Nu4dafoTkEC4h6dOiNBX9x1Eb3/JySoTavzXOSvxPB3B4T4+e8oXfXwqWZfOUQhZU 0dLdld58dDdoJ6rz6TB01uiXSSyK/OZSZoXaOeh5JkzIP/gOoabZG+KcAP/XhI39M8kD BS6Gb7evENcXk97cWMd09BqBaSOJh+bSgK8Z48r+JGdjMV2BB/j3PGcdFRlpNMnxwBmA BFTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=NpbJF6MT2O9ZRdv5/3zXZKe9fYIGN3f1O2lBE7v8CvU=; b=MT2uwjTAvvGZXIu1e78bllJvsk3GB+yKzLMVjfuas4Q9UyD3I51FoM0aVzFe+RZUaM smppXBBwjJNZsTCvNMeDewInNoBO2A5mE1GsqFj7ON2w20STxczj/szJLFr0qU3yFq/T UNjgxIt85cQ5nmj/72u9fGA1Zoj+rJ/S/hSHgU3n+JjGSX1tmpnuhThWPdUuuqZ7vawR E7Osdzmx5syOAbId/zp1IOV4m21daSZEOKUVNP0lfoqLzSCQ9odzZSoq2Mj8vAubEuA1 vgYqvNwbND2ojnWNoQ7CowHDbA7c/1/7mbH8VDBBJvEE2CMSTz0QpX80BmFU9OEBGkEP vX0Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s3si13717497otr.57.2020.01.16.15.57.01; Thu, 16 Jan 2020 15:57:13 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406902AbgAPSDf (ORCPT + 99 others); Thu, 16 Jan 2020 13:03:35 -0500 Received: from foss.arm.com ([217.140.110.172]:56900 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2393641AbgAPSDe (ORCPT ); Thu, 16 Jan 2020 13:03:34 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id DF3BD31B; Thu, 16 Jan 2020 10:03:33 -0800 (PST) Received: from donnerap.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id DE2C73F534; Thu, 16 Jan 2020 10:03:32 -0800 (PST) Date: Thu, 16 Jan 2020 18:03:26 +0000 From: Andre Przywara To: Radhey Shyam Pandey Cc: "David S . Miller" , Michal Simek , Robert Hancock , "netdev@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 03/14] net: axienet: Fix DMA descriptor cleanup path Message-ID: <20200116180326.47c93ce2@donnerap.cambridge.arm.com> In-Reply-To: References: <20200110115415.75683-1-andre.przywara@arm.com> <20200110115415.75683-4-andre.przywara@arm.com> <20200110154328.6676215f@donnerap.cambridge.arm.com> Organization: ARM X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; aarch64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 10 Jan 2020 17:05:45 +0000 Radhey Shyam Pandey wrote: Hi, > > -----Original Message----- > > From: Andre Przywara > > Sent: Friday, January 10, 2020 9:13 PM > > To: Radhey Shyam Pandey > > Cc: David S . Miller ; Michal Simek > > ; Robert Hancock ; > > netdev@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux- > > kernel@vger.kernel.org > > Subject: Re: [PATCH 03/14] net: axienet: Fix DMA descriptor cleanup path > > > > On Fri, 10 Jan 2020 15:14:46 +0000 > > Radhey Shyam Pandey wrote: > > > > Hi Radhey, > > > > thanks for having a look! > > > > > > -----Original Message----- > > > > From: Andre Przywara > > > > Sent: Friday, January 10, 2020 5:24 PM > > > > To: David S . Miller ; Radhey Shyam Pandey > > > > > > > > Cc: Michal Simek ; Robert Hancock > > > > ; netdev@vger.kernel.org; linux-arm- > > > > kernel@lists.infradead.org; linux-kernel@vger.kernel.org > > > > Subject: [PATCH 03/14] net: axienet: Fix DMA descriptor cleanup path > > > > > > > > When axienet_dma_bd_init() bails out during the initialisation process, > > > > it might do so with parts of the structure already allocated and > > > > initialised, while other parts have not been touched yet. Before > > > > returning in this case, we call axienet_dma_bd_release(), which does not > > > > take care of this corner case. > > > > This is most obvious by the first loop happily dereferencing > > > > lp->rx_bd_v, which we actually check to be non NULL *afterwards*. > > > > > > > > Make sure we only unmap or free already allocated structures, by: > > > > - directly returning with -ENOMEM if nothing has been allocated at all > > > > - checking for lp->rx_bd_v to be non-NULL *before* using it > > > > - only unmapping allocated DMA RX regions > > > > > > > > This avoids NULL pointer dereferences when initialisation fails. > > > > > > > > Signed-off-by: Andre Przywara > > > > --- > > > > .../net/ethernet/xilinx/xilinx_axienet_main.c | 43 ++++++++++++------- > > > > 1 file changed, 28 insertions(+), 15 deletions(-) > > > > > > > > diff --git a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c > > > > b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c > > > > index 97482cf093ce..7e90044cf2d9 100644 > > > > --- a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c > > > > +++ b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c > > > > @@ -160,24 +160,37 @@ static void axienet_dma_bd_release(struct > > > > net_device *ndev) > > > > int i; > > > > struct axienet_local *lp = netdev_priv(ndev); > > > > > > > > + /* If we end up here, tx_bd_v must have been DMA allocated. */ > > > > + dma_free_coherent(ndev->dev.parent, > > > > + sizeof(*lp->tx_bd_v) * lp->tx_bd_num, > > > > + lp->tx_bd_v, > > > > + lp->tx_bd_p); > > > > + > > > > + if (!lp->rx_bd_v) > > > > + return; > > > > + > > > > for (i = 0; i < lp->rx_bd_num; i++) { > > > > - dma_unmap_single(ndev->dev.parent, lp->rx_bd_v[i].phys, > > > > - lp->max_frm_size, DMA_FROM_DEVICE); > > > > + /* A NULL skb means this descriptor has not been initialised > > > > + * at all. > > > > + */ > > > > + if (!lp->rx_bd_v[i].skb) > > > > + break; > > > > + > > > > dev_kfree_skb(lp->rx_bd_v[i].skb); > > > > - } > > > > > > > > - if (lp->rx_bd_v) { > > > > - dma_free_coherent(ndev->dev.parent, > > > > - sizeof(*lp->rx_bd_v) * lp->rx_bd_num, > > > > - lp->rx_bd_v, > > > > - lp->rx_bd_p); > > > > - } > > > > - if (lp->tx_bd_v) { > > > > - dma_free_coherent(ndev->dev.parent, > > > > - sizeof(*lp->tx_bd_v) * lp->tx_bd_num, > > > > - lp->tx_bd_v, > > > > - lp->tx_bd_p); > > > > + /* For each descriptor, we programmed cntrl with the (non- > > > > zero) > > > > + * descriptor size, after it had been successfully allocated. > > > > + * So a non-zero value in there means we need to unmap it. > > > > + */ > > > > > > > + if (lp->rx_bd_v[i].cntrl) > > > > > > I think it should ok to unmap w/o any check? > > > > Do you mean because .phys would be 0 if not initialised? AFAIK 0 can be a > > valid DMA address, so there is no special check for that, and unmapping > > DMA address 0 will probably go wrong at some point. So it's unlike > > kfree(NULL). > > I mean if skb allocation is successful in _dma_bd_init then in release path > we can assume .phys is always a valid address and skip rx_bd_v[i].cntrl > check. I don't think we can assume this. If the skb allocation succeeded, but then the dma_map_single failed (which we check with dma_mapping_error()), we would end up with a valid skb, but an uninitialised phys DMA address in the registers. That's why I set .cntrl only after having checked the dma_map_single() result. Or am I missing something? Cheers, Andre > > > > + dma_unmap_single(ndev->dev.parent, lp- > > > > >rx_bd_v[i].phys, > > > > + lp->max_frm_size, > > > > DMA_FROM_DEVICE); > > > > } > > > > + > > > > + dma_free_coherent(ndev->dev.parent, > > > > + sizeof(*lp->rx_bd_v) * lp->rx_bd_num, > > > > + lp->rx_bd_v, > > > > + lp->rx_bd_p); > > > > } > > > > > > > > /** > > > > @@ -207,7 +220,7 @@ static int axienet_dma_bd_init(struct net_device > > > > *ndev) > > > > sizeof(*lp->tx_bd_v) * lp- > > > > >tx_bd_num, > > > > &lp->tx_bd_p, GFP_KERNEL); > > > > if (!lp->tx_bd_v) > > > > - goto out; > > > > + return -ENOMEM; > > > > > > > > lp->rx_bd_v = dma_alloc_coherent(ndev->dev.parent, > > > > sizeof(*lp->rx_bd_v) * lp- > > > > >rx_bd_num, > > > > -- > > > > 2.17.1 > > > >