[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZJ2bvm31vB2skuWQ1tTYhX41cXwX0EzUyb_1KFN_zSeuA@mail.gmail.com>
Date: Sun, 8 Jun 2014 12:16:53 +0300
From: Or Gerlitz <or.gerlitz@...il.com>
To: Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Wei Yang <weiyang@...ux.vnet.ibm.com>,
Or Gerlitz <ogerlitz@...lanox.com>,
David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>, Amir Vadai <amirv@...lanox.com>,
Jack Morgenstein <jackm@....mellanox.co.il>
Subject: Re: [PATCH net] net/mlx4_core: Fix Oops on reboot when SRIOV VFs are
probed into the Host
On Mon, Jun 2, 2014 at 7:10 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
[...]
> From the PCI core's perspective, after .probe() returns successfully,
> we can call any driver entry point and pass the pci_dev to it, and
> expect it to work. Doing mlx4_remove_one() in mlx4_pci_err_detected()
note that __mlx4_remove_one() is what called from mlx4_pci_err_detected()
and the former is built in a way which allows it to be called twice.
In that respect, I agree to the fix provided by Wei Yang over this thread, which
essentially makes .shutdown to behave in a similar way and call
__mlx4_remove_one()
and will submit it for inclusion.
> sort of breaks that assumption because you clear out pci_drvdata().
> Right now, the only other entry point mlx4 really implements is
> mlx4_remove_one(), and it has a hack that tests whether pci_drvdata()
> is NULL. But that's ... a hack, and you'll have to do the same
> if/when you implement suspend/resume/sriov_configure/etc.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists