Changing the MTU on a lagg device

[Pokala, Ravi]

Hi folks,

The attached patch works, but WITNESS found a LOR that may or may not be
strictly related. My test, and the associated messages, are in the
attached script.

There are actually *two* LOR messages. The first is when adding em1 to the
lagg, and it appears even without the patch, so that's because of the
patch. Though obviously, we should fix it. :-)

It's the *second* LOR that worries me, since it happens when I'm actually
calling SIOCSIFMTU on the component interfaces. I must admit ignorance
when it comes to deciphering WITNESS warnings; could someone explain what
it's trying to tell me?

Thanks,

Ravi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lagg_mtu.patch
Type: application/octet-stream
Size: 2521 bytes
Desc: lagg_mtu.patch
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20150210/a77a390b/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lagg_mtu.sh
Type: application/octet-stream
Size: 8986 bytes
Desc: lagg_mtu.sh
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20150210/a77a390b/attachment-0001.obj>