[snip] [snip] Thanks, I have added your Acks and queued-up this this change in ipvs-next. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo
Hello, v2 looks good, Acked-by: Julian Anastasov <ja@xxxxxx> Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message t
Thanks and sorry for missing that. How about this? ipvs: Use network byte order for sync message size struct ip_vs_sync_mesg and ip_vs_sync_mesg_v0 are both sent across the wire and used internally t
Hello, It seems v0 should be changed too, ip_vs_send_sync_msg() handles both versions in sb->mesg. Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe
Sure, sorry for not explaining myself more clearly. My idea is as follows: ipvs: Use network byte order for sync message size struct ip_vs_sync_mesg is both sent across the wire and used internally t
Hello, AFAIK, __force is the only way to suppress sparse warning. Not sure what is your idea, may be you can try it. Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the
I'm not very excited by the use of __force. Can't we change the type of the size element of struct ip_vs_sync_mesg and use the sparse annotations to our advantage? -- To unsubscribe from this list: s
Fix sparse warnings while changing the size between host and network order: net/netfilter/ipvs/ip_vs_sync.c:1179:20: warning: cast to restricted __be16 net/netfilter/ipvs/ip_vs_sync.c:1179:20: warnin