[PATCH v2 net-next 08/11] net: bridge: put SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS on the blocking call chain

[Vladimir Oltean]

From: Vladimir Oltean <vladimir.olt...@nxp.com>

Now that br_switchdev_set_port_flag is never called from under br->lock,
it runs in sleepable context.

All switchdev drivers handle SWITCHDEV_PORT_ATTR_SET as both blocking
and atomic, so no changes are needed on that front.

Signed-off-by: Vladimir Oltean <vladimir.olt...@nxp.com>
---
Changes in v2:
Patch is new.

 net/bridge/br_switchdev.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/net/bridge/br_switchdev.c b/net/bridge/br_switchdev.c
index bc63b10b2e67..3b152f2cd9b5 100644
--- a/net/bridge/br_switchdev.c
+++ b/net/bridge/br_switchdev.c
@@ -79,9 +79,8 @@ int br_switchdev_set_port_flag(struct net_bridge_port *p,
        attr.u.brport_flags.val = flags;
        attr.u.brport_flags.mask = mask;
 
-       /* We run from atomic context here */
-       err = call_switchdev_notifiers(SWITCHDEV_PORT_ATTR_SET, p->dev,
-                                      &info.info, extack);
+       err = call_switchdev_blocking_notifiers(SWITCHDEV_PORT_ATTR_SET, p->dev,
+                                               &info.info, extack);
        err = notifier_to_errno(err);
        if (err == -EOPNOTSUPP)
                return 0;
-- 
2.25.1