From: Raslan Darawsheh <rasland@nvidia.com>
To: Ali Alnubani <alialnu@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Michael Baum <michaelba@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/mlx5: fix build with clang 14
Date: Wed, 15 Jun 2022 10:08:22 +0000 [thread overview]
Message-ID: <BYAPR12MB3078B853CD3844008036FC1FCFAD9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220511164109.1574109-1-alialnu@nvidia.com>
Hi,
> -----Original Message-----
> From: Ali Alnubani <alialnu@nvidia.com>
> Sent: Wednesday, May 11, 2022 7:41 PM
> To: dev@dpdk.org
> Cc: Michael Baum <michaelba@nvidia.com>; stable@dpdk.org
> Subject: [PATCH v2] net/mlx5: fix build with clang 14
>
> Use fgets instead of fscanf to resolve the following warning reported by
> clang 14.0.0 in Fedora 37 (Rawhide):
>
> drivers/net/mlx5/linux/mlx5_ethdev_os.c:1137:52: error:
> 'fscanf' may overflow; destination buffer in argument 3 has size 16,
> but the corresponding specifier may require size 17
> [-Werror,-Wfortify-source]
> ret = fscanf(file, "%" RTE_STR(IF_NAMESIZE) "s", port_name);
>
> Fixes: 63d1db710fbc ("net/mlx5: fix unlimited parsing of switch info")
> Cc: michaelba@mellanox.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
> ---
> Changes in v2:
> - Removed unnecessary variable.
>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-06-15 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 13:58 [PATCH] " Ali Alnubani
2022-05-11 14:04 ` David Marchand
2022-05-11 16:41 ` [PATCH v2] " Ali Alnubani
2022-06-15 8:16 ` Thomas Monjalon
2022-06-15 8:41 ` David Marchand
2022-06-15 8:21 ` Slava Ovsiienko
2022-06-15 10:08 ` Raslan Darawsheh [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=BYAPR12MB3078B853CD3844008036FC1FCFAD9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=michaelba@nvidia.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).