This is the relevant commit: https://github.com/openvswitch/ovs/commit/b953042214201e2693a485a8ba8b19f69e5bdf34
Unfortunately, it's not very obvious from the commit message that this is a bug fix. On Sunday, November 8, 2015, ZHANG Zhiming <zhangzhim...@yunshan.net.cn> wrote: > Hi Gross, > > Thank you very much. > > You save me so much time. > > The version of OVS may not be changed due to some reasons. So I have to > fix it on versoin 2.31. > Could you tell me which patch solved this bug? > I checked a commit logs, and found no clues. > > Best regards, > > ------------------------------ > ZHANG Zhiming > Yunshan Networks > > *From:* Jesse Gross <javascript:_e(%7B%7D,'cvml','je...@nicira.com');> > *Date:* 2015-11-07 11:40 > *To:* zhangzhiming > <javascript:_e(%7B%7D,'cvml','zhangzhim...@yunshan.net.cn');> > *CC:* discuss <javascript:_e(%7B%7D,'cvml','discuss@openvswitch.org');> > *Subject:* Re: [ovs-discuss] ipfix leads to kernel crash > On Monday, November 2, 2015, ZHANG Zhiming <zhangzhim...@yunshan.net.cn > <javascript:_e(%7B%7D,'cvml','zhangzhim...@yunshan.net.cn');>> wrote: > >> Hi, >> >> Could someone help me check this kernel crash? >> I set ipfix to send report to a collector, and the kernel crashed after >> several hours. >> Thanks! >> >> ovs-vsctl (Open vSwitch) 2.3.1 >> Compiled Aug 11 2015 05:18:30 >> DB Schema 7.6.2 >> > > This bug has already been fixed. Please upgrade to either OVS 2.3.2 or > 2.4. >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
