On 12 July 2016 at 10:45, Martin Pieuchot wrote:
> dlg@ could reproduce a panic by running dhclient in a loop on one of his
> machines.
>
> Turns out that there's a race between arplookup() and arpcache() inside
> in_arpinput(). If another CPU removes the ARP entry from the table, via
> RTM_DELET
dlg@ could reproduce a panic by running dhclient in a loop on one of his
machines.
Turns out that there's a race between arplookup() and arpcache() inside
in_arpinput(). If another CPU removes the ARP entry from the table, via
RTM_DELETE, it will free the ARP storage. That means we cannot update