DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH 0/3] lib: remove use of strncpy
Date: Wed, 24 Jun 2026 09:53:33 +0800	[thread overview]
Message-ID: <e0fc2bb4-dfc3-4b6e-aece-a1a81ee78bb6@huawei.com> (raw)
In-Reply-To: <20260623141930.704771-1-bruce.richardson@intel.com>

Series-reviewed-by: Chengwen Feng <fengchengwen@huawei.com>

On 6/23/2026 10:19 PM, Bruce Richardson wrote:
> Taking a lead from the kernel, which has just finished a multi-year
> effort to remove use of strncpy[1], rework DPDK to remove use of the
> same function. This series removes all remaining uses of strncpy
> in lib directory.
> 
> [1] https://www.phoronix.com/news/Linux-7.2-Drops-strncpy
> 
> Bruce Richardson (3):
>   ethdev: remove use of strncpy
>   eventdev: improve bounds checks for names in adapter create
>   vhost: remove use of strncpy
> 
>  lib/ethdev/ethdev_driver.c              |  7 ++++++-
>  lib/eventdev/rte_event_eth_tx_adapter.c |  4 ++--
>  lib/vhost/socket.c                      |  4 +---
>  lib/vhost/vduse.c                       |  2 +-
>  lib/vhost/vhost.c                       | 12 +++---------
>  lib/vhost/vhost.h                       |  2 +-
>  6 files changed, 14 insertions(+), 17 deletions(-)
> 
> --
> 2.53.0
> 


      parent reply	other threads:[~2026-06-24  1:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 14:19 [PATCH 0/3] lib: remove use of strncpy Bruce Richardson
2026-06-23 14:19 ` [PATCH 1/3] ethdev: " Bruce Richardson
2026-06-23 14:19 ` [PATCH 2/3] eventdev: improve bounds checks for names in adapter create Bruce Richardson
2026-06-23 14:19 ` [PATCH 3/3] vhost: remove use of strncpy Bruce Richardson
2026-06-24  1:53 ` fengchengwen [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=e0fc2bb4-dfc3-4b6e-aece-a1a81ee78bb6@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /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