I'd like to try and reproduce this bug. Can you list the steps I would need to perform to reproduce the bug? Would it just be to use the Kopete client and try to connect to a jabber server?
Also, do I need to do some network reconfiguration? I am currently using IPv4, and do not have IPv6 configured.
I'm also going to build a test kernel for you to try with the following three commits reverted:
538c22c net/ipv6: Correct PIM6 mrt_lock handling
483d538 [stable-only] net: add length argument to skb_copy_and_csum_datagram_iov
16b7201 ipv6: fix exthdrs offload registration in out_rt path
If that does not fix the issue, we can perform a kernel bisect to identify the exact commit that introduced the regression.
Hi Pali,
I'd like to try and reproduce this bug. Can you list the steps I would need to perform to reproduce the bug? Would it just be to use the Kopete client and try to connect to a jabber server?
Also, do I need to do some network reconfiguration? I am currently using IPv4, and do not have IPv6 configured.
I'm also going to build a test kernel for you to try with the following three commits reverted: and_csum_ datagram_ iov
538c22c net/ipv6: Correct PIM6 mrt_lock handling
483d538 [stable-only] net: add length argument to skb_copy_
16b7201 ipv6: fix exthdrs offload registration in out_rt path
If that does not fix the issue, we can perform a kernel bisect to identify the exact commit that introduced the regression.