linux-kernel - RE: [PATCH 2/2] RDMA/rxe: Call rxe_set_mtu after rxe_register

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <OS7PR01MB1180411196785FFF5ECBC2965E51CA@OS7PR01MB11804.jpnprd01.prod.outlook.com>
Date:   Wed, 23 Aug 2023 02:46:40 +0000
From:   "Daisuke Matsuda (Fujitsu)" <matsuda-daisuke@...itsu.com>
To:     "Zhijian Li (Fujitsu)" <lizhijian@...itsu.com>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>
CC:     "zyjzyj2000@...il.com" <zyjzyj2000@...il.com>,
        "jgg@...pe.ca" <jgg@...pe.ca>, "leon@...nel.org" <leon@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "rpearsonhpe@...il.com" <rpearsonhpe@...il.com>,
        "Zhijian Li (Fujitsu)" <lizhijian@...itsu.com>
Subject: RE: [PATCH 2/2] RDMA/rxe: Call rxe_set_mtu after rxe_register_device

On Wed, Aug 23, 2023 11:13 AM Li Zhijian wrote:
> 
> rxe_set_mtu() will call rxe_info_dev() to print message, and
> rxe_info_dev() expects dev_name(rxe->ib_dev->dev) has been assigned.
> 
> Previously since dev_name() is not set, when a new rxe link is being
> added, 'null' will be used as the dev_name like:
> 
> "(null): rxe_set_mtu: Set mtu to 1024"
> 
> Move rxe_register_device() earlier to assign the correct dev_name
> so that it can be read by rxe_set_mtu() later.
> 
> And it's safe to do such change since mtu will not be used during the
> rxe_register_device()
> 
> After this change, message becomes:
> "rxe_eth0: rxe_set_mtu: Set mtu to 4096"
> 
> Signed-off-by: Li Zhijian <lizhijian@...itsu.com>
> ---
>  drivers/infiniband/sw/rxe/rxe.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/infiniband/sw/rxe/rxe.c b/drivers/infiniband/sw/rxe/rxe.c
> index cb2c0d54aae1..d29efce6e5ca 100644
> --- a/drivers/infiniband/sw/rxe/rxe.c
> +++ b/drivers/infiniband/sw/rxe/rxe.c
> @@ -169,10 +169,13 @@ void rxe_set_mtu(struct rxe_dev *rxe, unsigned int ndev_mtu)
>   */
>  int rxe_add(struct rxe_dev *rxe, unsigned int mtu, const char *ibdev_name)
>  {
> +	int ret;
> +
>  	rxe_init(rxe);
> +	ret = rxe_register_device(rxe, ibdev_name);
>  	rxe_set_mtu(rxe, mtu);
> 
> -	return rxe_register_device(rxe, ibdev_name);
> +	return ret;
>  }
> 
>  static int rxe_newlink(const char *ibdev_name, struct net_device *ndev)
> --
> 2.29.2

It makes sense.
Reviewed-by: Daisuke Matsuda <matsuda-daisuke@...itsu.com>