From: Xueming Li <xuemingl@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH 23.11] examples/ptpclient: fix message parsing
Date: Sat, 5 Apr 2025 07:38:29 +0000 [thread overview]
Message-ID: <CH3PR12MB8658C393F74857B2BE616926A1A82@CH3PR12MB8658.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250219171612.506172-1-stephen@networkplumber.org>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
Thanks, patch queued to 23.11.4 release staging
Regards,
Xueming
________________________________
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Thursday, February 20, 2025 1:16 AM
To: stable@dpdk.org <stable@dpdk.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 23.11] examples/ptpclient: fix message parsing
[ upstream commit 19630bd0d735badb06143086d4f1c50d726b7bad ]
Calling memcmp on same structure will always be true.
Replace with same conditional used elsewhere.
Link: https://pvs-studio.com/en/blog/posts/cpp/1183/
Fixes: ab129e9065a5 ("examples/ptpclient: add minimal PTP client")
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
examples/ptpclient/ptpclient.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/ptpclient/ptpclient.c b/examples/ptpclient/ptpclient.c
index cdf2da64df..92b54f240e 100644
--- a/examples/ptpclient/ptpclient.c
+++ b/examples/ptpclient/ptpclient.c
@@ -365,7 +365,7 @@ parse_sync(struct ptpv2_data_slave_ordinary *ptp_data, uint16_t rx_tstamp_idx)
ptp_data->ptpset = 1;
}
- if (memcmp(&ptp_hdr->source_port_id.clock_id,
+ if (memcmp(&ptp_hdr->master_clock_id,
&ptp_hdr->source_port_id.clock_id,
sizeof(struct clock_id)) == 0) {
--
2.47.2
[-- Attachment #2: Type: text/html, Size: 3375 bytes --]
next prev parent reply other threads:[~2025-04-05 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 17:16 Stephen Hemminger
2025-04-05 7:38 ` Xueming Li [this message]
2025-04-05 8:00 ` Xueming Li
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=CH3PR12MB8658C393F74857B2BE616926A1A82@CH3PR12MB8658.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=stable@dpdk.org \
--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).