[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <057735f0-4475-7a7b-815f-034b1095fa6c@gmail.com>
Date: Sat, 27 Apr 2019 16:52:31 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
David Ahern <dsahern@...il.com>,
"David S. Miller" <davem@...emloft.net>
Cc: Julian Anastasov <ja@....bg>, Cong Wang <xiyou.wangcong@...il.com>,
syzbot <syzbot+30209ea299c09d8785c9@...kaller.appspotmail.com>,
ddstreet@...e.org, dvyukov@...gle.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: unregister_netdevice: waiting for DEV to become free (2)
On 4/27/19 3:33 PM, Tetsuo Handa wrote:
>
> I'm waiting for davem why it is safe to move the dst entry from
> "a device to unregister" to "a loopback device in that namespace".
> I'm waiting for an explanation how the dst entry which was moved to
> "a loopback device in that namespace" is released (i.e. what the
> expected shutdown sequence is).
The most probable explanation is that we make sure the loopback device
is the last one to be dismantled at netns deletion,
and this would obviously happen after all dst have been released.
Powered by blists - more mailing lists