From: Thomas Monjalon <thomas@monjalon.net>
To: Harold Huang <baymaxhuang@gmail.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [PATCH v4] net/kni: reset rte_kni_conf struct before initialization
Date: Sun, 27 Feb 2022 21:12:52 +0100 [thread overview]
Message-ID: <4666160.Lt9SDvczpP@thomas> (raw)
In-Reply-To: <20211205062102.2165380-1-baymaxhuang@gmail.com>
+Cc Ferruh
05/12/2021 07:21, Harold Huang:
> When kni driver calls eth_kni_start to start device, some fields such as
> min_mtu and max_mtu of rte_kni_conf are not initialized. It will cause
> kni_ioctl_create create a kni netdevice with a random min_mtu and max_mtu
> value. This isunexpected and in some time we could not change the kni
> device mtu with ip link command.
>
> Fixes: ff1e35fb5f8 ("kni: calculate MTU from mbuf size")
> Signed-off-by: Harold Huang <baymaxhuang@gmail.com>
> ---
> drivers/net/kni/rte_eth_kni.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/kni/rte_eth_kni.c b/drivers/net/kni/rte_eth_kni.c
> index c428caf441..23b15edfac 100644
> --- a/drivers/net/kni/rte_eth_kni.c
> +++ b/drivers/net/kni/rte_eth_kni.c
> @@ -128,6 +128,7 @@ eth_kni_start(struct rte_eth_dev *dev)
> const char *name = dev->device->name + 4; /* remove net_ */
>
> mb_pool = internals->rx_queues[0].mb_pool;
> + memset(&conf, 0, sizeof(conf));
> strlcpy(conf.name, name, RTE_KNI_NAMESIZE);
> conf.force_bind = 0;
> conf.group_id = port_id;
next prev parent reply other threads:[~2022-02-27 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 7:24 [PATCH] " Harold Huang
2021-12-05 6:21 ` [PATCH v4] " Harold Huang
2022-02-27 20:12 ` Thomas Monjalon [this message]
2021-12-23 3:01 Harold Huang
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=4666160.Lt9SDvczpP@thomas \
--to=thomas@monjalon.net \
--cc=baymaxhuang@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).