Comment 9 for bug 1636708

> Why would bond0 get created when loading the bonding module?

Because the default module parameter max_bonds for bonding module is 1, meaning create one bond upon bond module loading.

I have since hit similar issue with networkd where bonding module would be autoprobed, bond0 created, and confuse networkd (bond0 already exists, not touching it).

I have since applied max_bonds=0 and used networkd. I guess I can try this again with ifupdown, max_bond=0, and check what sort of udev events are received.

Imho we should default to max_bonds=0 such that loading bonding module doesn't create stray interfaces.