From: Or Gerlitz <or.gerlitz@gmail.com>
To: Wei Yang <weiyang@linux.vnet.ibm.com>
Cc: Amir Vadai <amirv@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Yevgeny Petrilin <yevgenyp@mellanox.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH net-next] net/mlx4_core: Handle null return by pci_match_id()
Date: Mon, 31 Mar 2014 07:52:20 +0300 [thread overview]
Message-ID: <CAJZOPZKOPHDoBDSd7=ytbC8MfPPD_ZKBh6qrc0iA+mRF+FD6DQ@mail.gmail.com> (raw)
In-Reply-To: <20140331035439.GA11288@richard>
On Mon, Mar 31, 2014 at 6:54 AM, Wei Yang <weiyang@linux.vnet.ibm.com> wrote:
>
> On Sun, Mar 30, 2014 at 09:08:06PM +0300, Or Gerlitz wrote:
> >On Sun, Mar 30, 2014 at 6:26 PM, Amir Vadai <amirv@mellanox.com> wrote:
> >> Fix issue introduced by commit: 97a5221 "net/mlx4_core: pass
> >> pci_device_id.driver_data to __mlx4_init_one during reset".
> >>
> >> pci_match_id() might return NULL if someone binds the driver to a device
> >> manually using /sys/bus/pci/drivers/.../new_id. Need to check 'id'
> >> before using it.
> >>
> >> Thanks to Bjorn who raised the problem.
> >
> >Well, that commit was applied to net and is now present in Linus
> >tree... so assuming it's too late for 3.14, need to queue this for
> >-stable
> >
> >Or.
>
> Sorry for this bothering, hope this will not block someone.
>
> Here is my suggestion for fixing this, not sure this is a good way to export
> pci_match_device() to modules. This is my current solution to this problem. If
> you have any comments, please let me know.
>
> ------------------------------------------------------------------------------
> From 9361e1edd6776202c6e11dd44d3d4d72c990b111 Mon Sep 17 00:00:00 2001
> From: Wei Yang <weiyang@linux.vnet.ibm.com>
> Date: Mon, 31 Mar 2014 11:34:57 +0800
> Subject: [PATCH net-next] net/mlx4_core: match pci_device_id including dynids
Your original commit went to net and same needs to be done for the fix
>
>
> Fix issue introduced by commit: 97a5221 "net/mlx4_core: pass
> pci_device_id.driver_data to __mlx4_init_one during reset".
>
> pci_match_id() just match the static pci_device_id, which may return NULL if
> someone binds the driver to a device manually using
> /sys/bus/pci/drivers/.../new_id.
>
> This patch match pci_device_id with pci_match_device() to cover both dynids
> and static id_table.
>
> Thanks to Bjorn finding this issue.
>
> CC: Bjorn Helgaas <bhelgaas@google.com>
> CC: Amir Vadai <amirv@mellanox.com>
> Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
> ---
> drivers/net/ethernet/mellanox/mlx4/main.c | 4 +++-
> drivers/pci/pci-driver.c | 3 ++-
> include/linux/pci.h | 2 ++
> 3 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx4/main.c b/drivers/net/ethernet/mellanox/mlx4/main.c
> index aa54ef7..b0edb5c 100644
> --- a/drivers/net/ethernet/mellanox/mlx4/main.c
> +++ b/drivers/net/ethernet/mellanox/mlx4/main.c
> @@ -2673,7 +2673,9 @@ static pci_ers_result_t mlx4_pci_slot_reset(struct pci_dev *pdev)
> const struct pci_device_id *id;
> int ret;
>
> - id = pci_match_id(mlx4_pci_table, pdev);
> + id = pci_match_device(pci_dev_driver(pdev), pdev);
> + BUG_ON(!id);
> +
> ret = __mlx4_init_one(pdev, id->driver_data);
>
> return ret ? PCI_ERS_RESULT_DISCONNECT : PCI_ERS_RESULT_RECOVERED;
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index 25f0bc6..1ee26a1 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -225,7 +225,7 @@ const struct pci_device_id *pci_match_id(const struct pci_device_id *ids,
> * system is in its list of supported devices. Returns the matching
> * pci_device_id structure or %NULL if there is no match.
> */
> -static const struct pci_device_id *pci_match_device(struct pci_driver *drv,
> +const struct pci_device_id *pci_match_device(struct pci_driver *drv,
> struct pci_dev *dev)
> {
> struct pci_dynid *dynid;
> @@ -1355,6 +1355,7 @@ postcore_initcall(pci_driver_init);
>
> EXPORT_SYMBOL_GPL(pci_add_dynid);
> EXPORT_SYMBOL(pci_match_id);
> +EXPORT_SYMBOL(pci_match_device);
> EXPORT_SYMBOL(__pci_register_driver);
> EXPORT_SYMBOL(pci_unregister_driver);
> EXPORT_SYMBOL(pci_dev_driver);
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 6d1cc9e..d7a7d05 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -1135,6 +1135,8 @@ int pci_add_dynid(struct pci_driver *drv,
> unsigned long driver_data);
> const struct pci_device_id *pci_match_id(const struct pci_device_id *ids,
> struct pci_dev *dev);
> +const struct pci_device_id *pci_match_device(struct pci_driver *drv,
> + struct pci_dev *dev);
> int pci_scan_bridge(struct pci_bus *bus, struct pci_dev *dev, int max,
> int pass);
>
> --
> 1.7.9.5
>
>
> --
> Richard Yang
> Help you, Help me
>
next prev parent reply other threads:[~2014-03-31 4:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 15:26 [PATCH net-next] net/mlx4_core: Handle null return by pci_match_id() Amir Vadai
2014-03-30 18:08 ` Or Gerlitz
2014-03-31 3:54 ` Wei Yang
2014-03-31 4:52 ` Or Gerlitz [this message]
2014-03-31 6:29 ` Amir Vadai
2014-03-31 7:01 ` Wei Yang
2014-03-31 20:32 ` David Miller
2014-04-01 1:41 ` Wei Yang
2014-04-01 3:12 ` Bjorn Helgaas
2014-04-01 3:14 ` Wei Yang
2014-03-31 3:12 ` Wei Yang
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='CAJZOPZKOPHDoBDSd7=ytbC8MfPPD_ZKBh6qrc0iA+mRF+FD6DQ@mail.gmail.com' \
--to=or.gerlitz@gmail.com \
--cc=amirv@mellanox.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=weiyang@linux.vnet.ibm.com \
--cc=yevgenyp@mellanox.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).