From: David Ahern <dsahern@gmail.com>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
netdev@vger.kernel.org
Cc: chriscormier@cumulusnetworks.com, davem@davemloft.net
Subject: Re: [PATCH net] vrf: fix bug_on triggered by rx when destroying a vrf
Date: Thu, 6 Jul 2017 09:32:24 -0600 [thread overview]
Message-ID: <9f9c57d6-78db-7038-1992-7c4841b22ce9@gmail.com> (raw)
In-Reply-To: <1499343880-30421-1-git-send-email-nikolay@cumulusnetworks.com>
On 7/6/17 6:24 AM, Nikolay Aleksandrov wrote:
> When destroying a VRF device we cleanup the slaves in its ndo_uninit()
> function, but that causes packets to be switched (skb->dev == vrf being
> destroyed) even though we're pass the point where the VRF should be
> receiving any packets while it is being dismantled. This causes a BUG_ON
> to trigger if we have raw sockets (trace below).
> The reason is that the inetdev of the VRF has been destroyed but we're
> still sending packets up the stack with it, so let's free the slaves in
> the dellink callback as David Ahern suggested.
...
> Fixes: 193125dbd8eb ("net: Introduce VRF device driver")
> Reported-by: Chris Cormier <chriscormier@cumulusnetworks.com>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> ---
> drivers/net/vrf.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
Thanks for the fix.
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2017-07-06 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 12:24 [PATCH net] vrf: fix bug_on triggered by rx when destroying a vrf Nikolay Aleksandrov
2017-07-06 15:32 ` David Ahern [this message]
2017-07-06 15:47 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9f9c57d6-78db-7038-1992-7c4841b22ce9@gmail.com \
--to=dsahern@gmail.com \
--cc=chriscormier@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox