On Thu, 2016-09-08 at 17:35 -0700, Jojy Varghese wrote: > Thanks for the feedback guys. I appreciate it. > > I am working with 4.4.3 kernel. I will try to reproduce the issue > with the kernel tree at > https://git.kernel.org/cgit/linux/kernel/git/davem/net.git. >
Good. Please do not top post on netdev. > In the meantime, the only data I have now is : > - "dst-ifdown" does not look correct since it will never release > reference to loopback device. Normally at netns dismantle, all sockets and devices holding references to dst in this netns are closed and dst freed. Details are in various notifiers. At that time the dst->dev references will be released, including the ones having dst->dev == loopback (on the soon to be freed netns) We do not want to force in dst_ifdown() a dst->dev pointing nowhere, as it might crash say when dst->dev is used later during a sendmsg() or something like that. > - One way to fix might be to assign the 'dst''s net device to the > init net device. I thought adding reference to init net device's > loopback might be safe. > You only make _rebooting_ the host not possible, since the problem of having some reference on loopback device will still be there. We really have to find the root cause, not simply working around it.
