netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org,
	Alex Marginean <alexandru.marginean@nxp.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net-next] net: enetc: teardown CBDR during PF/VF unbind
Date: Fri, 19 Mar 2021 12:20:15 +0100	[thread overview]
Message-ID: <f64aeb3ed16df43363bbbbe5f8003785@walle.cc> (raw)
In-Reply-To: <20210319100806.801581-1-olteanv@gmail.com>

Am 2021-03-19 11:08, schrieb Vladimir Oltean:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
> 
> Michael reports that after the blamed patch, unbinding a VF would cause
> these transactions to remain pending, and trigger some warnings with 
> the
> DMA API debug:
> 
> $ echo 1 > /sys/bus/pci/devices/0000\:00\:00.0/sriov_numvfs
> pci 0000:00:01.0: [1957:ef00] type 00 class 0x020001
> fsl_enetc_vf 0000:00:01.0: Adding to iommu group 19
> fsl_enetc_vf 0000:00:01.0: enabling device (0000 -> 0002)
> fsl_enetc_vf 0000:00:01.0 eno0vf0: renamed from eth0
> 
> $ echo 0 > /sys/bus/pci/devices/0000\:00\:00.0/sriov_numvfs
> DMA-API: pci 0000:00:01.0: device driver has pending DMA allocations
> while released from device [count=1]
> One of leaked entries details: [size=2048 bytes] [mapped with
> DMA_BIDIRECTIONAL] [mapped as coherent]
> WARNING: CPU: 0 PID: 2547 at kernel/dma/debug.c:853
> dma_debug_device_change+0x174/0x1c8
> (...)
> Call trace:
>  dma_debug_device_change+0x174/0x1c8
>  blocking_notifier_call_chain+0x74/0xa8
>  device_release_driver_internal+0x18c/0x1f0
>  device_release_driver+0x20/0x30
>  pci_stop_bus_device+0x8c/0xe8
>  pci_stop_and_remove_bus_device+0x20/0x38
>  pci_iov_remove_virtfn+0xb8/0x128
>  sriov_disable+0x3c/0x110
>  pci_disable_sriov+0x24/0x30
>  enetc_sriov_configure+0x4c/0x108
>  sriov_numvfs_store+0x11c/0x198
> (...)
> DMA-API: Mapped at:
>  dma_entry_alloc+0xa4/0x130
>  debug_dma_alloc_coherent+0xbc/0x138
>  dma_alloc_attrs+0xa4/0x108
>  enetc_setup_cbdr+0x4c/0x1d0
>  enetc_vf_probe+0x11c/0x250
> pci 0000:00:01.0: Removing from iommu group 19
> 
> This happens because stupid me moved enetc_teardown_cbdr outside of
> enetc_free_si_resources, but did not bother to keep calling
> enetc_teardown_cbdr from all the places where enetc_free_si_resources
> was called. In particular, now it is no longer called from the main
> unbind function, just from the probe error path.
> 
> Fixes: 4b47c0b81ffd ("net: enetc: don't initialize unused ports from a
> separate code path")
> Reported-by: Michael Walle <michael@walle.cc>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>

Tested-by: Michael Walle <michael@walle.cc>

Thanks!

-michael

  reply	other threads:[~2021-03-19 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 10:08 [PATCH net-next] net: enetc: teardown CBDR during PF/VF unbind Vladimir Oltean
2021-03-19 11:20 ` Michael Walle [this message]
2021-03-19 19:20 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f64aeb3ed16df43363bbbbe5f8003785@walle.cc \
    --to=michael@walle.cc \
    --cc=alexandru.marginean@nxp.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=vladimir.oltean@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).