Re: [ovs-dev] [PATCH] pkt reassemble: fix kernel panic for ovs reassemble

Thanks Joe. BR, Wang Zhike -Original Message- From: Joe Stringer [mailto:j...@ovn.org] Sent: Saturday, July 22, 2017 2:29 AM To: 王志克 Cc: ovs dev; Ben Pfaff Subject: Re: [ovs-dev] [PATCH] pkt reassemble: fix kernel panic for ovs reassemble On 6 July 2017 at 13:57, Ben Pfaff &l

Re: [ovs-dev] [PATCH] pkt reassemble: fix kernel panic for ovs reassemble

On 6 July 2017 at 13:57, Ben Pfaff wrote: > From: wangzhike > > 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

[ovs-dev] [PATCH] pkt reassemble: fix kernel panic for ovs reassemble

From: wangzhike 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

Re: [ovs-dev] [PATCH] pkt reassemble: fix kernel panic for ovs reassemble

On 21 June 2017 at 18:54, 王志克 wrote: > 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

[ovs-dev] [PATCH] pkt reassemble: fix kernel panic for ovs reassemble

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.