V1.7.8 release #487
Merged
V1.7.8 release #487
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mismatch of rte_lcore_id and rte_socket_id
…vice in function dp_vs_get_svc; it may cause dpvs crash when keepalived restart.
fix ipvsadm conhash support
fix bug for get service/dest（double free）
remove trailing space
ip_vs_service.c: fix possible use after free
keepalived: fix crash when remove all RS(s) from virtual service group
ip_vs_dest.c: remove useless codes
During nat64 test, the below issue is met on IPv6-side (aka wan side).
Provided that dpvs's gateway IPv6 address is fcbd:dc00:46::1.
1) When the outgoing packet destined to IPv6 client is sent out from dpvs, we
need to resolve dpvs's gateway mac address. So the below neighbour
solicitation is sent from dpvs to its IPv6 gateway.
(:: -> ff02::1:ff00:1) that includes info, "Neighbour Solicitation for
fcbd:dc00:46::1".
And the related neighbour entry, E1, is created on core A.
E1: (fcbd:dc00:46::1, 00:00:00:00:00:00, dpdk1, DPVS_NUD_S_SEND)
2) The coresponding neighbour advertisement is received on core B.
(fe80:274:9cff:fe0e:1441 -> ff02::1) that includes info, "Neighbour
Advertisement fcbd:dc00:46::1 (rtr, ovr) is at 00:74:9c:0e:14:41".
Also within ndisc_recv_na(), target address, "fcbd:dc00:46::1" should
be used to find the neighbour entry instead of source-ip address,
"fe80:274:9cff:fe0e:1441".
Since the neighbour entry is not found on core B, we just create the below
entry, E2 directly with the state of "DPVS_NUD_S_REACHABLE" and then sync it
to the other cores. Lastly, the entry, E1 created on core A gets resolved
accordingly.
E2: (fcbd:dc00:46::1, 00:74:9c:0e:14:41, dpdk1, DPVS_NUD_S_REACHABLE)
* do not unlock handler in timer_expire for global timer * remove lock for per-lcore timer
* simplify refcnt for multicast msg
* use hash table to collect reply msg from slaves for multicast msg
* fix multicast msg register problem
* fix dead problem partly when slaves' reply msg send to master fail
timer: add dummy info for crash problem
mscbg
approved these changes
Nov 4, 2019
ytwang0320
pushed a commit
to ytwang0320/dpvs
that referenced
this pull request
Dec 22, 2020
V1.7.8 release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[ Feature ]
[ Bugfix ]