Le 31/05/2016 08:29, Vincent Bernat a écrit : > ❦ 30 mai 2016 18:27 CEST, Nicolas Dichtel <nicolas.dich...@6wind.com> : > >>>> + >>>> + rtmsg_ifinfo(RTM_NEWLINK, peer, IFF_SLAVE, GFP_KERNEL); >>> >>> Maybe ~0U would be better than hijacking IFF_SLAVE? >> IFF_SLAVE is wrong. It's a flag here, that will be put in the ifi_change >> field >> not an attribute number. > > There are some use of IFF_SLAVE (in bonding/bond_main.c). But, I'll > update the patch nonetheless. Sorry, I read it too quickly, IFF_SLAVE is a flag, not an attribute. But this field indicates to the userland which flags has changed and this flag does not change here ;-)
- [PATCH] veth: delay peer link configuration after interfa... Vincent Bernat
- Re: [PATCH] veth: delay peer link configuration afte... Nicolas Dichtel
- Re: [PATCH] veth: delay peer link configuration after int... Vincent Bernat
- Re: [PATCH] veth: delay peer link configuration afte... Nicolas Dichtel
- Re: [PATCH] veth: delay peer link configuration ... Vincent Bernat
- Re: [PATCH] veth: delay peer link configurat... Nicolas Dichtel
- [net v3] veth: advertise peer link once ... Vincent Bernat
- Re: [net v3] veth: advertise peer l... Vincent Bernat
- Re: [net v3] veth: advertise peer l... Nicolas Dichtel
- Re: [net v3] veth: advertise peer l... Vincent Bernat
- Re: [net v3] veth: advertise peer l... Nicolas Dichtel
- Re: [net v3] veth: advertise peer l... Lance Richardson
- Re: [net v3] veth: advertise peer l... Nicolas Dichtel
- Re: [net v3] veth: advertise peer l... Lance Richardson
- [net v4] veth: advertise peer link ... Vincent Bernat
- Re: [net v4] veth: advertise peer l... Vincent Bernat