After a review, Yakkety did get the following commits via other bug reports:
d37117d ethernet: use net core MTU range checking in more drivers
6426a88 net: use core MTU range checking in virt drivers
89110d9 net: use core MTU range checking in virt drivers
e84f31d net: centralize net_device min/max MTU checking
fe5473b hv_netvsc: remove excessive logging on MTU change
This changed the MTU checking in some places and not all. I think commits 91572088e3f and 3331aa378e9b are needed.
I built a V2 Yakkety test kernel with these two commits. It can be downloaded from:
After a review, Yakkety did get the following commits via other bug reports:
d37117d ethernet: use net core MTU range checking in more drivers
6426a88 net: use core MTU range checking in virt drivers
89110d9 net: use core MTU range checking in virt drivers
e84f31d net: centralize net_device min/max MTU checking
fe5473b hv_netvsc: remove excessive logging on MTU change
This changed the MTU checking in some places and not all. I think commits 91572088e3f and 3331aa378e9b are needed.
I built a V2 Yakkety test kernel with these two commits. It can be downloaded from:
http:// kernel. ubuntu. com/~jsalisbury /lp1679823/
Can folks affected by this bug give this kernel a test?
Thanks in advance!