public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: courmisch@gmail.com, Yajun Deng <yajun.deng@linux.dev>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] net: Adjustment parameters in rtnl_notify()
Date: Mon, 19 Jul 2021 17:36:06 +0300	[thread overview]
Message-ID: <5299846.uZDWVASI8p@basile.remlab.net> (raw)
In-Reply-To: <20210719122506.5414-1-yajun.deng@linux.dev>

 Hi,

Le maanantaina 19. heinäkuuta 2021, 15.25.06 EEST Yajun Deng a écrit :
> The fifth parameter alread modify from 'struct nlmsghdr *nlh' to
> 'int report', just adjustment them.

I can't see that anywhere in the patch.

> Add the case the nlh variable is NULL in nlmsg_report().
> 
> Signed-off-by: Yajun Deng <yajun.deng@linux.dev>

> diff --git a/net/phonet/pn_netlink.c b/net/phonet/pn_netlink.c
> index 59aebe296890..03e04d0b8453 100644
> --- a/net/phonet/pn_netlink.c
> +++ b/net/phonet/pn_netlink.c
> @@ -38,7 +38,7 @@ void phonet_address_notify(int event, struct net_device
> *dev, u8 addr) goto errout;
>  	}
>  	rtnl_notify(skb, dev_net(dev), 0,
> -		    RTNLGRP_PHONET_IFADDR, NULL, GFP_KERNEL);
> +		    RTNLGRP_PHONET_IFADDR, 0, GFP_KERNEL);
>  	return;
>  errout:
>  	rtnl_set_sk_err(dev_net(dev), RTNLGRP_PHONET_IFADDR, err);
> @@ -204,7 +204,7 @@ void rtm_phonet_notify(int event, struct net_device
> *dev, u8 dst) goto errout;
>  	}
>  	rtnl_notify(skb, dev_net(dev), 0,
> -			  RTNLGRP_PHONET_ROUTE, NULL, GFP_KERNEL);
> +			  RTNLGRP_PHONET_ROUTE, 0, GFP_KERNEL);
>  	return;
>  errout:
>  	rtnl_set_sk_err(dev_net(dev), RTNLGRP_PHONET_ROUTE, err);

Sorry but I don't like to replace explicit NULL pointers with implicitly 
converted zeroes.

-- 
雷米‧德尼-库尔蒙
http://www.remlab.net/




  reply	other threads:[~2021-07-19 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 12:25 [PATCH 2/4] net: Adjustment parameters in rtnl_notify() Yajun Deng
2021-07-19 14:36 ` Rémi Denis-Courmont [this message]
2021-07-20  3:24   ` yajun.deng

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=5299846.uZDWVASI8p@basile.remlab.net \
    --to=remi@remlab.net \
    --cc=courmisch@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yajun.deng@linux.dev \
    /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