Thanks, got it. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-i
Hello, Of course, it is for 3.5 and 3.4-stable (3.4+) Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to major
Hello, Only for 3.4-stable, it seems Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxx
Hello, I now see why I didn't noticed it. net: In unregister_netdevice_notifier unregister the netdevices. It seems I tested with tree without this change, there is 18-19 days gap. It oopses because
Thanks, will do. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-
Hello, Yes, oops happened to me. I'm not sure how I missed it while creating the mentioned change. Please, queue it for stable kernels. Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from
Hi Julian, have you observed this oops or is it theoretical? I ask because it effects if I should submit this change for inclusion in 3.5 and 3.4-stable or just queue it up for 3.6. Thanks. -- To uns
After commit 39f618b4fd95ae243d940ec64c961009c74e3333 (3.4) "ipvs: reset ipvs pointer in netns" we can oops in ip_vs_dst_event on rmmod ip_vs because ip_vs_control_cleanup is called after the ipvs_co