DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: <longli@linuxonhyperv.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Wei Hu" <weh@microsoft.com>
Cc: <dev@dpdk.org>, "Long Li" <longli@microsoft.com>
Subject: RE: [PATCH] net/mana: avoid the use of variable length array
Date: Wed, 5 Mar 2025 10:00:33 +0100	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9FABF@smartserver.smartshare.dk> (raw)
In-Reply-To: <1741135052-2039-1-git-send-email-longli@linuxonhyperv.com>

> From: longli@linuxonhyperv.com [mailto:longli@linuxonhyperv.com]
> Sent: Wednesday, 5 March 2025 01.38
> 
> From: Long Li <longli@microsoft.com>
> 
> The pathname can be defined as name[MAX_PATH]. This makes the driver
> compilable using MSVC.

The name is PATH_MAX, not MAX_PATH. It's correct in the code.

> 
> Signed-off-by: Long Li <longli@microsoft.com>
> ---
>  drivers/net/mana/mana.c | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/net/mana/mana.c b/drivers/net/mana/mana.c
> index c37c4e3444..d12dff6ce1 100644
> --- a/drivers/net/mana/mana.c
> +++ b/drivers/net/mana/mana.c
> @@ -36,11 +36,8 @@ static rte_spinlock_t mana_shared_data_lock =
> RTE_SPINLOCK_INITIALIZER;
> 
>  /* Allocate a buffer on the stack and fill it with a printf format
> string. */
>  #define MANA_MKSTR(name, ...) \

The macro is no longer generic, but tied to a path name, so the macro's name and description should be updated accordingly. E.g.:

/* Allocate a path name buffer on the stack and fill it with a printf format string. */
#define MANA_MKPATHSTR(name, ...) \

Don't forget search-replace for uses of the macro. (It's being used 6 times in this file.)

> -	int mkstr_size_##name = snprintf(NULL, 0, "" __VA_ARGS__); \
> -	char name[mkstr_size_##name + 1]; \
> -	\
> -	memset(name, 0, mkstr_size_##name + 1); \
> -	snprintf(name, sizeof(name), "" __VA_ARGS__)
> +	char name[PATH_MAX]; \
> +	snprintf(name, PATH_MAX, "" __VA_ARGS__)
> 
>  int mana_logtype_driver;
>  int mana_logtype_init;
> --
> 2.34.1

With suggested changes,
Acked-by: Morten Brørup <mb@smartsharesystems.com>


  reply	other threads:[~2025-03-05  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  0:37 longli
2025-03-05  9:00 ` Morten Brørup [this message]
2025-03-06  2:17 ` Andre Muezerie

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=98CBD80474FA8B44BF855DF32C47DC35E9FABF@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=dev@dpdk.org \
    --cc=longli@linuxonhyperv.com \
    --cc=longli@microsoft.com \
    --cc=stephen@networkplumber.org \
    --cc=weh@microsoft.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).