From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, vivien.didelot@savoirfairelinux.com,
andrew@lunn.ch, jiri@resnulli.us, marcelo.leitner@gmail.com,
Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH net-next v2 0/4] net: switchdev: Avoid sleep in atomic with DSA
Date: Mon, 9 Jan 2017 12:45:19 -0800 [thread overview]
Message-ID: <20170109204523.5843-1-f.fainelli@gmail.com> (raw)
Hi all,
This patch series is to resolve a sleeping function called in atomic context
debug splat that we observe with DSA.
Let me know what you think, I was also wondering if we should just always
make switchdev_port_vlan_fill() set SWITCHDEV_F_DEFER, but was afraid this
could cause invalid contexts to be used for rocker, mlxsw, i40e etc.
Changes in v2:
- Make patch 3 actually build, thanks to Marcelo for reporting the
problem
Thanks!
Florian Fainelli (4):
net: switchdev: Prepare for deferred functions modifying objects
net: switchdev: Add object dump deferred operation
net: switchdev: Add switchdev_port_bridge_getlink_deferred
net: dsa: Utilize switchdev_port_bridge_getlink_deferred()
include/net/switchdev.h | 3 +
net/dsa/slave.c | 2 +-
net/switchdev/switchdev.c | 171 +++++++++++++++++++++++++++++++++++++---------
3 files changed, 141 insertions(+), 35 deletions(-)
--
2.9.3
next reply other threads:[~2017-01-09 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 20:45 Florian Fainelli [this message]
2017-01-09 20:45 ` [PATCH net-next v2 1/4] net: switchdev: Prepare for deferred functions modifying objects Florian Fainelli
2017-01-10 10:09 ` Jiri Pirko
2017-01-10 17:57 ` Florian Fainelli
2017-01-09 20:45 ` [PATCH net-next v2 2/4] net: switchdev: Add object dump deferred operation Florian Fainelli
2017-01-09 20:45 ` [PATCH net-next v2 3/4] net: switchdev: Add switchdev_port_bridge_getlink_deferred Florian Fainelli
2017-01-09 20:45 ` [PATCH net-next v2 4/4] net: dsa: Utilize switchdev_port_bridge_getlink_deferred() Florian Fainelli
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=20170109204523.5843-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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;
as well as URLs for NNTP newsgroup(s).