From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbox@nvidia.com>,
Huawei Xie <huawei.xhw@alibaba-inc.com>,
Jianfeng Tan <jianfeng.tan@intel.com>
Subject: Re: [PATCH 2/2] net/virtio: fix fortify memcpy warning
Date: Tue, 28 May 2024 23:33:56 +0200 [thread overview]
Message-ID: <5882415.zQ0Gbyo6oJ@thomas> (raw)
In-Reply-To: <20240521010105.81868-2-stephen@networkplumber.org>
21/05/2024 03:01, Stephen Hemminger:
> If fortify is enabled, it will generate a warning if memcpy
> src is NULL even if size is zero. This happens if the MP message
> sync is called with no file descriptors.
>
> Bugzilla ID 1446
> Fixes: 6a84c37e3975 ("net/virtio-user: add vhost-user adapter layer")
Bugzilla ID: 1446
Fixes: 6a84c37e3975 ("net/virtio-user: add vhost-user adapter layer")
Cc: stable@dpdk.org
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Series applied quickly as it is blocking compilation on recent Ubuntu.
prev parent reply other threads:[~2024-05-28 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 1:01 [PATCH 1/2] pcapng: fix fortified " Stephen Hemminger
2024-05-21 1:01 ` [PATCH 2/2] net/virtio: fix fortify " Stephen Hemminger
2024-05-28 21:33 ` Thomas Monjalon [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=5882415.zQ0Gbyo6oJ@thomas \
--to=thomas@monjalon.net \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=huawei.xhw@alibaba-inc.com \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=stephen@networkplumber.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).