From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: Zhang Chen <chen.zhang@intel.com>,
Jason Wang <jasowang@redhat.com>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Cc: Tao Xu <tao3.xu@intel.com>, qemu-dev <qemu-devel@nongnu.org>
Subject: Re: [PATCH 4/4] net/colo.c: fix segmentation fault when packet is not parsed correctly
Date: Mon, 21 Mar 2022 03:39:50 +0000 [thread overview]
Message-ID: <3ad2a276-faf7-a94b-59fd-dd405d97a3c0@fujitsu.com> (raw)
In-Reply-To: <20220309083858.58117-5-chen.zhang@intel.com>
On 09/03/2022 16:38, Zhang Chen wrote:
> When COLO use only one vnet_hdr_support parameter between
> filter-redirector and filter-mirror(or colo-compare), COLO will crash
> with segmentation fault. Back track as follow:
>
> Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault.
> 0x0000555555cb200b in eth_get_l2_hdr_length (p=0x0)
> at /home/tao/project/COLO/colo-qemu/include/net/eth.h:296
> 296 uint16_t proto = be16_to_cpu(PKT_GET_ETH_HDR(p)->h_proto);
> (gdb) bt
> 0 0x0000555555cb200b in eth_get_l2_hdr_length (p=0x0)
> at /home/tao/project/COLO/colo-qemu/include/net/eth.h:296
> 1 0x0000555555cb22b4 in parse_packet_early (pkt=0x555556a44840) at
> net/colo.c:49
> 2 0x0000555555cb2b91 in is_tcp_packet (pkt=0x555556a44840) at
> net/filter-rewriter.c:63
>
> So wrong vnet_hdr_len will cause pkt->data become NULL.
Not sure if we can check this earlier, well
Reviewed-by: Li Zhijian <lizhijian@fujitsu.com>
> Add check to
> raise error and add trace-events to track vnet_hdr_len.
>
> Signed-off-by: Tao Xu <tao3.xu@intel.com>
> Signed-off-by: Zhang Chen <chen.zhang@intel.com>
> ---
> net/colo.c | 9 ++++++++-
> net/trace-events | 1 +
> 2 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/net/colo.c b/net/colo.c
> index 694f3c93ef..6b0ff562ad 100644
> --- a/net/colo.c
> +++ b/net/colo.c
> @@ -46,7 +46,14 @@ int parse_packet_early(Packet *pkt)
> static const uint8_t vlan[] = {0x81, 0x00};
> uint8_t *data = pkt->data + pkt->vnet_hdr_len;
> uint16_t l3_proto;
> - ssize_t l2hdr_len = eth_get_l2_hdr_length(data);
> + ssize_t l2hdr_len;
> +
> + if (data == NULL) {
> + trace_colo_proxy_main_vnet_info("This packet is not parsed correctly, "
> + "pkt->vnet_hdr_len", pkt->vnet_hdr_len);
> + return 1;
> + }
> + l2hdr_len = eth_get_l2_hdr_length(data);
>
> if (pkt->size < ETH_HLEN + pkt->vnet_hdr_len) {
> trace_colo_proxy_main("pkt->size < ETH_HLEN");
> diff --git a/net/trace-events b/net/trace-events
> index d7a17256cc..6af927b4b9 100644
> --- a/net/trace-events
> +++ b/net/trace-events
> @@ -9,6 +9,7 @@ vhost_user_event(const char *chr, int event) "chr: %s got event: %d"
>
> # colo.c
> colo_proxy_main(const char *chr) ": %s"
> +colo_proxy_main_vnet_info(const char *sta, int size) ": %s = %d"
>
> # colo-compare.c
> colo_compare_main(const char *chr) ": %s"
prev parent reply other threads:[~2022-03-21 3:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 8:38 [PATCH 0/4] COLO net and runstate bugfix/optimization Zhang Chen
2022-03-09 8:38 ` [PATCH 1/4] softmmu/runstate.c: add RunStateTransition support form COLO to PRELAUNCH Zhang Chen
2022-03-09 8:38 ` [PATCH 2/4] net/colo: Fix a "double free" crash to clear the conn_list Zhang Chen
2022-03-21 3:05 ` lizhijian
2022-03-28 9:13 ` Zhang, Chen
2022-03-31 1:14 ` lizhijian
2022-03-31 2:25 ` Zhang, Chen
2022-04-01 1:46 ` lizhijian
2022-04-01 3:33 ` Zhang, Chen
2022-03-09 8:38 ` [PATCH 3/4] net/colo.c: No need to track conn_list for filter-rewriter Zhang Chen
2022-03-21 3:16 ` lizhijian
2022-03-09 8:38 ` [PATCH 4/4] net/colo.c: fix segmentation fault when packet is not parsed correctly Zhang Chen
2022-03-21 3:39 ` lizhijian [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=3ad2a276-faf7-a94b-59fd-dd405d97a3c0@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=chen.zhang@intel.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tao3.xu@intel.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).