Anton Blanchard <anton@xxxxxxxxx> wrote:
>
>
> > which is SIOCGIFADDR. It seems to me the down() is actually the
> > rtnl_lock() called at net/ipv4/devinet.c:536 in devinet_ioctl. This
> > happens even when netplugd is no longer running. It looks like someone
> > isn't releasing the lock.
> >
> > I'm going over all the uses of rtnl_lock() to see if I can find a
> > problem, but no sign yet. I wonder if someone might have broken this
> > recently: I'm running 2.6.0-test4-mm6, but I think Bryan is running an
> > older kernel (2.6.0-test4?), and hasn't seen any problems.
>
> Yep I saw this too when updating from test2 to BK from a few days ago.
> >From memory the cpu that had the rtnl_lock was stuck in dev_close,
> probably netif_poll_disable. I got side tracked and wasnt able to look
> into it.
If the caller of netif_poll_disable() has a signal pending,
netif_poll_disable() becomes a busy loop, which might be causing a
lockup. Probably not, but it needs to use TASK_UNINTERRUPTIBLE.
I doubt if that explains Jeremy's deadlock though...
|