netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
	 davem@davemloft.net, edumazet@google.com, parav@nvidia.com
Subject: Re: [patch net] devlink: fix port new reply cmd type
Date: Mon, 18 Mar 2024 19:54:53 +0530	[thread overview]
Message-ID: <CAH-L+nP-xV03WE4aXsQoN5Ph3j+BO=uoGCDurqtUiUp+e27TDQ@mail.gmail.com> (raw)
In-Reply-To: <20240318091908.2736542-1-jiri@resnulli.us>

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

On Mon, Mar 18, 2024 at 2:49 PM Jiri Pirko <jiri@resnulli.us> wrote:
>
> From: Jiri Pirko <jiri@nvidia.com>
>
> Due to a c&p error, port new reply fills-up cmd with wrong value,
> any other existing port command replies and notifications.
>
> Fix it by filling cmd with value DEVLINK_CMD_PORT_NEW.
>
> Skimmed through devlink userspace implementations, none of them cares
> about this cmd value.
>
> Reported-by: Chenyuan Yang <chenyuan0y@gmail.com>
> Closes: https://lore.kernel.org/all/ZfZcDxGV3tSy4qsV@cy-server/
> Fixes: cd76dcd68d96 ("devlink: Support add and delete devlink port")
> Signed-off-by: Jiri Pirko <jiri@nvidia.com>

LGTM,
Reviewed-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> ---
>  net/devlink/port.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/devlink/port.c b/net/devlink/port.c
> index 4b2d46ccfe48..118d130d2afd 100644
> --- a/net/devlink/port.c
> +++ b/net/devlink/port.c
> @@ -889,7 +889,7 @@ int devlink_nl_port_new_doit(struct sk_buff *skb, struct genl_info *info)
>                 err = -ENOMEM;
>                 goto err_out_port_del;
>         }
> -       err = devlink_nl_port_fill(msg, devlink_port, DEVLINK_CMD_NEW,
> +       err = devlink_nl_port_fill(msg, devlink_port, DEVLINK_CMD_PORT_NEW,
>                                    info->snd_portid, info->snd_seq, 0, NULL);
>         if (WARN_ON_ONCE(err))
>                 goto err_out_msg_free;
> --
> 2.44.0
>
>


-- 
Regards,
Kalesh A P

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4239 bytes --]

  parent reply	other threads:[~2024-03-18 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18  9:19 [patch net] devlink: fix port new reply cmd type Jiri Pirko
2024-03-18 13:57 ` Parav Pandit
2024-03-18 14:21   ` Jiri Pirko
2024-03-18 14:24 ` Kalesh Anakkur Purayil [this message]
2024-03-20  3:10 ` patchwork-bot+netdevbpf

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='CAH-L+nP-xV03WE4aXsQoN5Ph3j+BO=uoGCDurqtUiUp+e27TDQ@mail.gmail.com' \
    --to=kalesh-anakkur.purayil@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.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).