DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Evgeny Sokolov <Evgeny.Sokolov@infotecs.ru>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>, <dev@dpdk.org>,
	<stable@dpdk.org>, <mukawa@igel.co.jp>
Subject: Re: [PATCH 5/5] Replacing the unsafe strcpy function
Date: Tue, 15 Sep 2026 06:26:23 -0700	[thread overview]
Message-ID: <20260915062623.1bd5041b@phoenix.local> (raw)
In-Reply-To: <20260915095846.432214-1-Evgeny.Sokolov@infotecs.ru>

On Tue, 15 Sep 2026 09:58:46 +0000
Evgeny Sokolov <Evgeny.Sokolov@infotecs.ru> wrote:

> From: Sokolov Evgeny <Evgeny.Sokolov@infotecs.ru>
> 
> ---
>  lib/ethdev/rte_ethdev.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
> index 55ea8fe808..b040f9fa84 100644
> --- a/lib/ethdev/rte_ethdev.c
> +++ b/lib/ethdev/rte_ethdev.c
> @@ -718,7 +718,7 @@ rte_eth_dev_get_name_by_port(uint16_t port_id, char *name)
>  	tmp = eth_dev_shared_data->data[port_id].name;
>  	rte_spinlock_unlock(rte_mcfg_ethdev_get_lock());
>  
> -	strcpy(name, tmp);
> +	strncpy(name, tmp, RTE_ETH_NAME_MAX_LEN);
>  
>  	rte_ethdev_trace_get_name_by_port(port_id, name);
>  


This has already been addressed for 26.11 by 

https://patchwork.dpdk.org/project/dpdk/patch/20260806174755.890910-1-stephen@networkplumber.org/

      reply	other threads:[~2026-09-15 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  9:58 [PATCH 5/5] Replacing the unsafe strcpy function Evgeny Sokolov
2026-09-15 13:26 ` Stephen Hemminger [this message]

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=20260915062623.1bd5041b@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=Evgeny.Sokolov@infotecs.ru \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=mukawa@igel.co.jp \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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