From: Jason Wang <jasowang@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Fan Yang" <Fan_Yang@sjtu.edu.cn>,
qemu-devel@nongnu.org, "Zhang Chen" <chen.zhang@intel.com>,
"Li Zhijian" <lizhijian@cn.fujitsu.com>
Subject: Re: [PATCH] COLO-compare: Fix incorrect `if` logic
Date: Wed, 25 Sep 2019 12:20:33 +0800 [thread overview]
Message-ID: <413e09c6-9376-5021-bf69-c3797237ae9d@redhat.com> (raw)
In-Reply-To: <6d23190f-e68a-3000-c288-84f2e0d50b07@redhat.com>
On 2019/9/24 下午11:35, Philippe Mathieu-Daudé wrote:
> Hi Fan,
>
> you forgot to Cc the maintainers (doing that for you):
>
> ./scripts/get_maintainer.pl -f net/colo-compare.c
> Zhang Chen <chen.zhang@intel.com> (supporter:COLO Proxy)
> Li Zhijian <lizhijian@cn.fujitsu.com> (supporter:COLO Proxy)
> Jason Wang <jasowang@redhat.com> (maintainer:Network device ba...)
> qemu-devel@nongnu.org (open list:All patches CC here)
>
> On 9/24/19 4:08 PM, Fan Yang wrote:
>> 'colo_mark_tcp_pkt' should return 'true' when packets are the same, and
>> 'false' otherwise. However, it returns 'true' when
>> 'colo_compare_packet_payload' returns non-zero while
>> 'colo_compare_packet_payload' is just a 'memcmp'. The result is that
>> COLO-compare reports inconsistent TCP packets when they are actually
>> the same.
>>
> Fixes: f449c9e549c
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Applied.
Thanks
>
>> Signed-off-by: Fan Yang <Fan_Yang@sjtu.edu.cn>
>> ---
>> net/colo-compare.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/net/colo-compare.c b/net/colo-compare.c
>> index 7489840bde..7ee17f2cf8 100644
>> --- a/net/colo-compare.c
>> +++ b/net/colo-compare.c
>> @@ -319,7 +319,7 @@ static bool colo_mark_tcp_pkt(Packet *ppkt, Packet *spkt,
>> *mark = 0;
>>
>> if (ppkt->tcp_seq == spkt->tcp_seq && ppkt->seq_end == spkt->seq_end) {
>> - if (colo_compare_packet_payload(ppkt, spkt,
>> + if (!colo_compare_packet_payload(ppkt, spkt,
>> ppkt->header_size, spkt->header_size,
>> ppkt->payload_size)) {
>> *mark = COLO_COMPARE_FREE_SECONDARY | COLO_COMPARE_FREE_PRIMARY;
>> @@ -329,7 +329,7 @@ static bool colo_mark_tcp_pkt(Packet *ppkt, Packet *spkt,
>>
>> /* one part of secondary packet payload still need to be compared */
>> if (!after(ppkt->seq_end, spkt->seq_end)) {
>> - if (colo_compare_packet_payload(ppkt, spkt,
>> + if (!colo_compare_packet_payload(ppkt, spkt,
>> ppkt->header_size + ppkt->offset,
>> spkt->header_size + spkt->offset,
>> ppkt->payload_size - ppkt->offset)) {
>> @@ -348,7 +348,7 @@ static bool colo_mark_tcp_pkt(Packet *ppkt, Packet *spkt,
>> /* primary packet is longer than secondary packet, compare
>> * the same part and mark the primary packet offset
>> */
>> - if (colo_compare_packet_payload(ppkt, spkt,
>> + if (!colo_compare_packet_payload(ppkt, spkt,
>> ppkt->header_size + ppkt->offset,
>> spkt->header_size + spkt->offset,
>> spkt->payload_size - spkt->offset)) {
>>
next prev parent reply other threads:[~2019-09-25 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 14:08 [PATCH] COLO-compare: Fix incorrect `if` logic Fan Yang
2019-09-24 15:35 ` Philippe Mathieu-Daudé
2019-09-25 4:20 ` Jason Wang [this message]
2019-09-25 5:53 ` Fan Yang
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=413e09c6-9376-5021-bf69-c3797237ae9d@redhat.com \
--to=jasowang@redhat.com \
--cc=Fan_Yang@sjtu.edu.cn \
--cc=chen.zhang@intel.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).