[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181123203958.GJ3395@ziepe.ca>
Date: Fri, 23 Nov 2018 13:39:58 -0700
From: Jason Gunthorpe <jgg@...pe.ca>
To: "Wei Hu (Xavier)" <xavier.huwei@...wei.com>
Cc: dledford@...hat.com, linux-rdma@...r.kernel.org,
lijun_nudt@....com, oulijun@...wei.com, charles.chenxin@...wei.com,
liuyixian@...wei.com, zhangxiping3@...wei.com, linuxarm@...wei.com,
linux-kernel@...r.kernel.org, xavier_huwei@....com
Subject: Re: [PATCH rdma-next 3/3] RDMA/hns: Modify hns RoCE device's name
On Fri, Nov 23, 2018 at 11:14:25PM +0800, Wei Hu (Xavier) wrote:
> This patch modifies the name of hns RoCE device's name in order
> to ensure that the name is consistent before and after reset.
>
> Signed-off-by: Wei Hu (Xavier) <xavier.huwei@...wei.com>
> drivers/infiniband/hw/hns/hns_roce_device.h | 1 +
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 3 +++
> drivers/infiniband/hw/hns/hns_roce_main.c | 4 +++-
> 3 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/hns/hns_roce_device.h b/drivers/infiniband/hw/hns/hns_roce_device.h
> index 259977b..a8cfe76 100644
> +++ b/drivers/infiniband/hw/hns/hns_roce_device.h
> @@ -954,6 +954,7 @@ struct hns_roce_dev {
> struct pci_dev *pci_dev;
> struct device *dev;
> struct hns_roce_uar priv_uar;
> + char name[IB_DEVICE_NAME_MAX];
> const char *irq_names[HNS_ROCE_MAX_IRQ_NUM];
> spinlock_t sm_lock;
> spinlock_t bt_cmd_lock;
> diff --git a/drivers/infiniband/hw/hns/hns_roce_hw_v2.c b/drivers/infiniband/hw/hns/hns_roce_hw_v2.c
> index 1d639a0..678c7ec 100644
> +++ b/drivers/infiniband/hw/hns/hns_roce_hw_v2.c
> @@ -6110,6 +6110,9 @@ static int hns_roce_hw_v2_get_cfg(struct hns_roce_dev *hr_dev,
> hr_dev->irq[i] = pci_irq_vector(handle->pdev,
> i + handle->rinfo.base_vector);
>
> + snprintf(hr_dev->name, IB_DEVICE_NAME_MAX, "hns%s",
> + handle->rinfo.netdev->name);
Why is this making up its own driver name? How is this avoiding
colliding with an existing name?
This is very dangerous since we now have device renaming, the driver
could fail to load with no recovery.
Jason
Powered by blists - more mailing lists