Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkt reassemble: fix kernel panic for ovs reassemble #187

Closed
wants to merge 1 commit into from
Closed

pkt reassemble: fix kernel panic for ovs reassemble #187

wants to merge 1 commit into from

Conversation

wangzk320
Copy link
Contributor

Ovs and kernel stack would add frag_queue to same netns_frags list.
As result, ovs and kernel may access the fraq_queue without correct
lock. Also the struct ipq may be different on kernel(older than 4.3),
which leads to invalid pointer access.

The fix creates specific netns_frags for ovs.

Signed-off-by: wangzhike wangzhike@jd.com

Ovs and kernel stack would add frag_queue to same netns_frags list.
As result, ovs and kernel may access the fraq_queue without correct
lock. Also the struct ipq may be different on kernel(older than 4.3),
which leads to invalid pointer access.

The fix creates specific netns_frags for ovs.

Signed-off-by: wangzhike <wangzhike@jd.com>
@blp
Copy link
Contributor

blp commented Jul 6, 2017

I posted this to ovs-dev to make sure that it gets noticed.

@joestringer
Copy link
Contributor

Thanks again for investigating this and sorry it took so long to test it out. Unfortunately this code is very prone to affecting rare race conditions, so it is a difficult thing to get confidence about the potential impact in conjunction with different kernel releases.

I applied this:
https://mail.openvswitch.org/pipermail/ovs-dev/2017-July/336087.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants