From: David Miller <davem@davemloft.net>
To: anoob.soman@citrix.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v3 net] packet: Do not call fanout_release from atomic contexts
Date: Fri, 17 Feb 2017 11:13:33 -0500 (EST) [thread overview]
Message-ID: <20170217.111333.106912523796144773.davem@davemloft.net> (raw)
In-Reply-To: <1487190339-6366-1-git-send-email-anoob.soman@citrix.com>
From: Anoob Soman <anoob.soman@citrix.com>
Date: Wed, 15 Feb 2017 20:25:39 +0000
> Commit 6664498280cf ("packet: call fanout_release, while UNREGISTERING a
> netdev"), unfortunately, introduced the following issues.
...
> To fix the above problems, remove the call to fanout_release() under
> rcu_read_lock(). Instead, call __dev_remove_pack(&fanout->prot_hook) and
> netdev_run_todo will be happy that &dev->ptype_specific list is empty. In order
> to achieve this, I moved dev_{add,remove}_pack() out of fanout_{add,release} to
> __fanout_{link,unlink}. So, call to {,__}unregister_prot_hook() will make sure
> fanout->prot_hook is removed as well.
>
> Fixes: 6664498280cf ("packet: call fanout_release, while UNREGISTERING a netdev")
> Reported-by: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Anoob Soman <anoob.soman@citrix.com>
> ---
> Changes in v3:
> - Removed extra variable from fanout_release(), per Eric's suggestion.
> Changes in v2:
> - Incorporated Eric's suggestion to do fanout_release_data() and kfree() after
> synchronize_net()
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2017-02-17 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 20:25 [PATCH v3 net] packet: Do not call fanout_release from atomic contexts Anoob Soman
2017-02-15 21:02 ` Eric Dumazet
2017-02-15 21:30 ` Anoob Soman
2017-02-15 21:34 ` Eric Dumazet
2017-02-15 21:33 ` Eric Dumazet
2017-02-17 16:13 ` David Miller [this message]
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=20170217.111333.106912523796144773.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=anoob.soman@citrix.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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