linux-kernel - Aw: RE: [PATCH net] net: hns: Fix the device being used for dma mapping during TX

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]

Message-ID: <trinity-0f73c31c-c719-4bc7-83f8-f5d01426e42b-1486731703602@3capp-gmx-bs14>
Date:   Fri, 10 Feb 2017 14:01:43 +0100
From:   "Lino Sanfilippo" <LinoSanfilippo@....de>
To:     "Salil Mehta" <salil.mehta@...wei.com>
Cc:     "davem@...emloft.net" <davem@...emloft.net>,
        "Zhuangyuzeng (Yisen)" <yisen.zhuang@...wei.com>,
        "mehta.salil.lnk@...il.com" <mehta.salil.lnk@...il.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Linuxarm <linuxarm@...wei.com>,
        "Yankejian (Hackim Yim)" <yankejian@...wei.com>
Subject: Aw: RE: [PATCH net] net: hns: Fix the device being used for dma
 mapping during TX



> Gesendet: Donnerstag, 09. Februar 2017 um 12:30 Uhr
> Von: "Salil Mehta" <salil.mehta@...wei.com>
> An: "Lino Sanfilippo" <LinoSanfilippo@....de>
> Cc: "davem@...emloft.net" <davem@...emloft.net>, "Zhuangyuzeng (Yisen)" <yisen.zhuang@...wei.com>, "mehta.salil.lnk@...il.com" <mehta.salil.lnk@...il.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Linuxarm <linuxarm@...wei.com>, "Yankejian (Hackim Yim)" <yankejian@...wei.com>
> Betreff: RE: [PATCH net] net: hns: Fix the device being used for dma mapping during TX
>
> > -----Original Message-----
> > From: Lino Sanfilippo [mailto:LinoSanfilippo@....de]
> > Sent: Thursday, February 09, 2017 10:25 AM
> > To: Salil Mehta
> > Cc: davem@...emloft.net; Salil Mehta; Zhuangyuzeng (Yisen);
> > mehta.salil.lnk@...il.com; netdev@...r.kernel.org; linux-
> > kernel@...r.kernel.org; Linuxarm; Yankejian (Hackim Yim)
> > Subject: Re: [PATCH net] net: hns: Fix the device being used for dma
> > mapping during TX
> > 
> > Hi,
> > 
> > > From: Kejian Yan <yankejian@...wei.com>
> > >
> > > This patch fixes the device being used to DMA map skb->data.
> > > Erroneous device assignment causes the crash when SMMU is enabled.
> > > This happens during TX since buffer gets DMA mapped with device
> > > correspondign to net_device and gets unmapped using the device
> > > related to DSAF.
> > >
> > > Signed-off-by: Kejian Yan <yankejian@...wei.com>
> > > Reviewed-by: Yisen Zhuang <yisen.zhuang@...wei.com>
> > > Signed-off-by: Salil Mehta <salil.mehta@...wei.com>
> > > ---
> > >  drivers/net/ethernet/hisilicon/hns/hns_enet.c |    2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/net/ethernet/hisilicon/hns/hns_enet.c
> > b/drivers/net/ethernet/hisilicon/hns/hns_enet.c
> > > index 672b646..2b52a12 100644
> > > --- a/drivers/net/ethernet/hisilicon/hns/hns_enet.c
> > > +++ b/drivers/net/ethernet/hisilicon/hns/hns_enet.c
> > > @@ -305,7 +305,7 @@ int hns_nic_net_xmit_hw(struct net_device *ndev,
> > >  			struct hns_nic_ring_data *ring_data)
> > >  {
> > >  	struct hns_nic_priv *priv = netdev_priv(ndev);
> > > -	struct device *dev = priv->dev;
> > > +	struct device *dev = ring_to_dev(ring_data->ring);
> > >  	struct hnae_ring *ring = ring_data->ring;
> > >  	struct netdev_queue *dev_queue;
> > >  	struct skb_frag_struct *frag;
> > > --
> > 
> > I would say it should be the other way around: Use priv->dev for
> > mapping and
> > unmapping instead of ring_to_dev().
> Yes, you got it right. Ideally, it should be per-port and for
> legacy reasons we have it this way. In the current design, we have
> SMMU node per-dsaf and I guess we will not land in the right
> dma-ops if we use per-netdev platform-device/device right now.
> 

Ok, but how can it work if we set the DMA mask of the device object of 
the plaform_device (via dma_set_mask_and_coherent in the probe() function)
and do the actual mapping with a different device object? I dont know much about
 the low level dma handling but I can imagine that the mask is required to
do the mapping correctly. 

Regards,
Lino