On 12 March 2015 at 10:39, Martin Pieuchot <[email protected]> wrote: > On 12/03/15(Thu) 09:53, Henk Jan Agteresch wrote: >> On Tue, 10 Mar 2015, Martin Pieuchot wrote: >> >> > >> > Here's a first diff that should prevent the stack smashing. Could you >> > run with it and tell me if the ARP entry gets overwritten as in 5.5? >> > >> >> Patch works for me. Arp entry gets overwritten. No more panics during >> network configuring. >> >> # dmesg |grep arp >> arpresolve: 213.154.229.23: incorrect arp information >> arpresolve: 213.154.229.23: incorrect arp information >> arpresolve: 213.154.229.23: incorrect arp information >> arpresolve: 213.154.229.23: incorrect arp information >> arpresolve: 213.154.229.23: incorrect arp information >> arp info overwritten for 213.154.229.23 by fe:54:00:b2:8c:98 on pcn0 > > Thanks for testing, I'll try to cook another diff to not encode the name > of the interface in the arp information. > > Here's the same diff with the nit pointed by krw@ fixed, any ok? >
So how can this happen? What kind of incorrect ARP information is it? Where does it come from? And why didn't we see that before?
