From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:30
This is a heads-up to DSA driver maintainers: in about 3 weeks time
(when the development cycle for v5.16 begins), I will come back with
these patches and attempt to drop the rtnl_lock guarantee from the DSA
.port_fdb_add and .port_fdb_del methods.
Plans might change, but this seems like an overall beneficial change if
we could make it, regardless of whether it is going to be part of the
final solution for enforcing FDB isolation in DSA.
After applying the entire patch set, the .port_fdb_add and .port_fdb_del
methods will run unlocked, and I would appreciate any regression test
that a maintainer can run on their hardware. Most drivers have locking
of sorts, but I wouldn't trust it, since it wasn't really put to test
until now.
The change set is structured as follows (from bottom to top):
1. A self test that driver maintainers could run while testing their
newly unlocked ops. It is not bullet-proof, but I have found issues
with it, so maybe it is useful.
To run it, rsync the entire "selftests" folder to the board, then run:
./selftests/drivers/net/dsa/test_bridge_fdb_stress.sh sw0p2
For the sja1105 driver, this was an indication that the internal
locking was not sufficient:
[ 282.615386] sja1105 spi2.0: port 2 failed to read back entry for 00:01:02:03:04:05 vid 1: -ENOENT <- printed by the driver
[ 282.624796] sja1105 spi2.0: port 2 failed to add 00:01:02:03:04:05 vid 1 to fdb: -2 <- printed by DSA
The self-test does not test traffic, but it would be nice to check if
the switch still behaves normally after the test finishes.
2. The DSA changes themselves that drop the rtnl_lock.
3. Some example changes that I needed to make in two drivers I could
test. I would very much prefer avoiding non-expert, wide ranging
locking schemes such as an "FDB lock" or a "register lock". It is
best to understand what needs to be atomic and what can be safely
concurrent.
As usual, feedback and ACKs/NACKs are very welcome.
Vladimir Oltean (8):
net: dsa: sja1105: wait for dynamic config command completion on
writes too
net: dsa: sja1105: serialize access to the dynamic config interface
net: mscc: ocelot: serialize access to the MAC table
net: dsa: introduce locking for the address lists on CPU and DSA ports
net: dsa: drop rtnl_lock from dsa_slave_switchdev_event_work
net: dsa: flush switchdev workqueue when leaving the bridge
selftests: lib: forwarding: allow tests to not require mz and jq
selftests: net: dsa: add a stress test for unlocked FDB operations
MAINTAINERS | 1 +
drivers/net/dsa/sja1105/sja1105.h | 2 +
.../net/dsa/sja1105/sja1105_dynamic_config.c | 91 ++++++++++++++-----
drivers/net/dsa/sja1105/sja1105_main.c | 1 +
drivers/net/ethernet/mscc/ocelot.c | 53 ++++++++---
include/net/dsa.h | 1 +
include/soc/mscc/ocelot.h | 3 +
net/dsa/dsa.c | 5 +
net/dsa/dsa2.c | 1 +
net/dsa/dsa_priv.h | 2 +
net/dsa/port.c | 2 +
net/dsa/slave.c | 2 -
net/dsa/switch.c | 76 +++++++++++-----
.../drivers/net/dsa/test_bridge_fdb_stress.sh | 48 ++++++++++
tools/testing/selftests/net/forwarding/lib.sh | 10 +-
15 files changed, 235 insertions(+), 63 deletions(-)
create mode 100755 tools/testing/selftests/drivers/net/dsa/test_bridge_fdb_stress.sh
--
2.25.1
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:31
The hardware manual says that software should attempt a new dynamic
config access (be it a a write or a read-back) only while the VALID bit
is cleared. The VALID bit is set by software to 1, and it remains set as
long as the hardware is still processing the request.
Currently the driver only polls for the command completion only for
reads, because that's when we need the actual data read back. Writes
have been more or less "asynchronous", although this has never been an
observable issue.
This change makes sja1105_dynamic_config_write poll the VALID bit as
well, to absolutely ensure that a follow-up access to the static config
finds the VALID bit cleared.
So VALID means "work in progress", while VALIDENT means "entry being
read is valid". On reads we check the VALIDENT bit too, while on writes
that bit is not always defined. So we need to factor it out of the loop,
and make the loop provide back the unpacked command structure, so that
sja1105_dynamic_config_read can check the VALIDENT bit.
The change also attempts to convert the open-coded loop to use the
read_poll_timeout macro, since I know this will come up during review.
It's more code, but hey, it uses read_poll_timeout!
Tested on SJA1105T, SJA1105S, SJA1110A.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
.../net/dsa/sja1105/sja1105_dynamic_config.c | 81 ++++++++++++++-----
1 file changed, 59 insertions(+), 22 deletions(-)
@@ -1170,6 +1170,56 @@ const struct sja1105_dynamic_table_ops sja1110_dyn_ops[BLK_IDX_MAX_DYN] = {},};+#define SJA1105_DYNAMIC_CONFIG_SLEEP_US 10+#define SJA1105_DYNAMIC_CONFIG_TIMEOUT_US 100000++staticint+sja1105_dynamic_config_poll_valid(structsja1105_private*priv,+structsja1105_dyn_cmd*cmd,+conststructsja1105_dynamic_table_ops*ops)+{+u8packed_buf[SJA1105_MAX_DYN_CMD_SIZE]={};+intrc;++/* We don't _need_ to read the full entry, just the command area which+*isafixedSJA1105_SIZE_DYN_CMD.Butourcmd_packing()APIexpectsa+*bufferthatcontainsthefullentrytoo.Additionally,ourAPI+*doesn'treallyknowhowmanybytesintothebufferdoesthecommand+*areareallybegin.Sojustreadbackthewholeentry.+*/+rc=sja1105_xfer_buf(priv,SPI_READ,ops->addr,packed_buf,+ops->packed_size);+if(rc)+returnrc;++/* Unpack the command structure, and return it to the caller in case it+*needstoperformfurtherchecksonit(VALIDENT).+*/+memset(cmd,0,sizeof(*cmd));+ops->cmd_packing(packed_buf,cmd,UNPACK);++/* Hardware hasn't cleared VALID => still working on it */+returncmd->valid?-EAGAIN:0;+}++/* Poll the dynamic config entry's control area until the hardware has+*clearedtheVALIDbit,whichmeanswehaveconfirmationthatithas+*finishedprocessingthecommand.+*/+staticint+sja1105_dynamic_config_wait_complete(structsja1105_private*priv,+structsja1105_dyn_cmd*cmd,+conststructsja1105_dynamic_table_ops*ops)+{+intrc;++returnread_poll_timeout(sja1105_dynamic_config_poll_valid,+rc,rc!=-EAGAIN,+SJA1105_DYNAMIC_CONFIG_SLEEP_US,+SJA1105_DYNAMIC_CONFIG_TIMEOUT_US,+false,priv,cmd,ops);+}+/* Provides read access to the settings through the dynamic interface*oftheswitch.*@blk_idxisusedaskeytoselectfromthesja1105_dynamic_table_ops.
@@ -1239,28 +1288,12 @@ int sja1105_dynamic_config_read(struct sja1105_private *priv,if(rc<0)returnrc;-/* Loop until we have confirmation that hardware has finished-*processingthecommandandhasclearedtheVALIDfield-*/-do{-memset(packed_buf,0,ops->packed_size);--/* Retrieve the read operation's result */-rc=sja1105_xfer_buf(priv,SPI_READ,ops->addr,packed_buf,-ops->packed_size);-if(rc<0)-returnrc;--cmd=(structsja1105_dyn_cmd){0};-ops->cmd_packing(packed_buf,&cmd,UNPACK);--if(!cmd.valident&&!(ops->access&OP_VALID_ANYWAY))-return-ENOENT;-cpu_relax();-}while(cmd.valid&&--retries);+rc=sja1105_dynamic_config_wait_complete(priv,&cmd,ops);+if(rc<0)+returnrc;-if(cmd.valid)-return-ETIMEDOUT;+if(!cmd.valident&&!(ops->access&OP_VALID_ANYWAY))+return-ENOENT;/* Don't dereference possibly NULL pointer - maybe caller*onlywantedtoseewhethertheentryexistedornot.
@@ -1321,6 +1354,10 @@ int sja1105_dynamic_config_write(struct sja1105_private *priv,if(rc<0)returnrc;+rc=sja1105_dynamic_config_wait_complete(priv,&cmd,ops);+if(rc<0)+returnrc;+cmd=(structsja1105_dyn_cmd){0};ops->cmd_packing(packed_buf,&cmd,UNPACK);if(cmd.errors)
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:34
The sja1105 hardware seems as concurrent as can be, but when we create a
background script that adds/removes a rain of FDB entries without the
rtnl_mutex taken, then in parallel we do another operation like run
'bridge fdb show', we can notice these errors popping up:
sja1105 spi2.0: port 2 failed to read back entry for 00:01:02:03:00:40 vid 0: -ENOENT
sja1105 spi2.0: port 2 failed to add 00:01:02:03:00:40 vid 0 to fdb: -2
sja1105 spi2.0: port 2 failed to read back entry for 00:01:02:03:00:46 vid 0: -ENOENT
sja1105 spi2.0: port 2 failed to add 00:01:02:03:00:46 vid 0 to fdb: -2
Luckily what is going on does not require a major rework in the driver.
The sja1105_dynamic_config_read() function sends multiple SPI buffers to
the peripheral until the operation completes. We should not do anything
until the hardware clears the VALID bit.
But since there is no locking (i.e. right now we are implicitly
serialized by the rtnl_mutex, but if we remove that), it might be
possible that the process which performs the dynamic config read is
preempted and another one performs a dynamic config write.
What will happen in that case is that sja1105_dynamic_config_read(),
when it resumes, expects to see VALIDENT set for the entry it reads
back. But it won't.
This can be corrected by introducing a mutex for serializing SPI
accesses to the dynamic config interface which should be atomic with
respect to each other.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
drivers/net/dsa/sja1105/sja1105.h | 2 ++
drivers/net/dsa/sja1105/sja1105_dynamic_config.c | 12 ++++++++++--
drivers/net/dsa/sja1105/sja1105_main.c | 1 +
3 files changed, 13 insertions(+), 2 deletions(-)
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:37
This test is a bit strange in that it is perhaps more manual than
others: it does not transmit a clear OK/FAIL verdict, because user space
does not have synchronous feedback from the kernel. If a hardware access
fails, it is in deferred context.
Nonetheless, on sja1105 I have used it successfully to find and solve a
concurrency issue, so it can be used as a starting point for other
driver maintainers too.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
MAINTAINERS | 1 +
.../drivers/net/dsa/test_bridge_fdb_stress.sh | 48 +++++++++++++++++++
2 files changed, 49 insertions(+)
create mode 100755 tools/testing/selftests/drivers/net/dsa/test_bridge_fdb_stress.sh
@@ -0,0 +1,48 @@+#!/bin/bash+# SPDX-License-Identifier: GPL-2.0++# Bridge FDB entries can be offloaded to DSA switches without holding the+# rtnl_mutex. Traditionally this mutex has conferred drivers implicit+# serialization, which means their code paths are not well tested in the+# presence of concurrency.+# This test creates a background task that stresses the FDB by adding and+# deleting an entry many times in a row without the rtnl_mutex held.+# It then tests the driver resistance to concurrency by calling .ndo_fdb_dump+# (with rtnl_mutex held) from a foreground task.+# Since either the FDB dump or the additions/removals can fail, but the+# additions and removals are performed in deferred as opposed to process+# context, we cannot simply check for user space error codes.++WAIT_TIME=1+NUM_NETIFS=1+REQUIRE_JQ="no"+REQUIRE_MZ="no"+NETIF_CREATE="no"+lib_dir=$(dirname$0)/../../../net/forwarding+source$lib_dir/lib.sh++cleanup(){+echo"Cleaning up"+iplinkdelbr0+kill$pid+killallbash+echo"Please check kernel log for errors"+}+trap'cleanup'EXIT++eth=${NETIFS[p1]}++iplinkdelbr02&>1>/dev/null||:+iplinkaddbr0typebridge&&iplinkset$ethmasterbr0++(while:;do+bridgefdbadd00:01:02:03:04:05dev$ethmasterstatic+bridgefdbdel00:01:02:03:04:05dev$ethmasterstatic+done)&+pid=$!++foriin$(seq150);do+bridgefdbshow>/dev/null+sleep3+echo"$((${i}*2))% complete..."+done
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:39
Now that the rtnl_mutex is going away for dsa_port_{host_,}fdb_{add,del},
no one is serializing access to the address lists that DSA keeps for the
purpose of reference counting on shared ports (CPU and cascade ports).
It can happen for one dsa_switch_do_fdb_del to do list_del on a dp->fdbs
element while another dsa_switch_do_fdb_{add,del} is traversing dp->fdbs.
We need to avoid that.
Currently dp->mdbs is not at risk, because dsa_switch_do_mdb_{add,del}
still runs under the rtnl_mutex. But it would be nice if it would not
depend on that being the case. So let's introduce a mutex per port (the
address lists are per port too) and share it between dp->mdbs and
dp->fdbs.
The place where we put the locking is interesting. It could be tempting
to put a DSA-level lock which still serializes calls to
.port_fdb_{add,del}, but it would still not avoid concurrency with other
driver code paths that are currently under rtnl_mutex (.port_fdb_dump,
.port_fast_age). So it would add a very false sense of security (and
adding a global switch-wide lock in DSA to resynchronize with the
rtnl_lock is also counterproductive and hard).
So the locking is intentionally done only where the dp->fdbs and dp->mdbs
lists are traversed. That means, from a driver perspective, that
.port_fdb_add will be called with the dp->addr_lists_lock mutex held on
the CPU port, but not held on user ports. This is done so that driver
writers are not encouraged to rely on any guarantee offered by
dp->addr_lists_lock.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
include/net/dsa.h | 1 +
net/dsa/dsa2.c | 1 +
net/dsa/switch.c | 76 ++++++++++++++++++++++++++++++++---------------
3 files changed, 54 insertions(+), 24 deletions(-)
@@ -285,6 +285,7 @@ struct dsa_port {/* List of MAC addresses that must be forwarded on this port.*TheseareonlyvalidonCPUportsandDSAlinks.*/+structmutexaddr_lists_lock;structlist_headfdbs;structlist_headmdbs;
@@ -214,26 +214,30 @@ static int dsa_switch_do_mdb_add(struct dsa_switch *ds, int port,{structdsa_port*dp=dsa_to_port(ds,port);structdsa_mac_addr*a;-interr;+interr=0;/* No need to bother with refcounting for user ports */if(!(dsa_port_is_cpu(dp)||dsa_port_is_dsa(dp)))returnds->ops->port_mdb_add(ds,port,mdb);+mutex_lock(&dp->addr_lists_lock);+a=dsa_mac_addr_find(&dp->mdbs,mdb->addr,mdb->vid);if(a){refcount_inc(&a->refcount);-return0;+gotoout;}a=kzalloc(sizeof(*a),GFP_KERNEL);-if(!a)-return-ENOMEM;+if(!a){+err=-ENOMEM;+gotoout;+}err=ds->ops->port_mdb_add(ds,port,mdb);if(err){kfree(a);-returnerr;+gotoout;}ether_addr_copy(a->addr,mdb->addr);
@@ -241,7 +245,10 @@ static int dsa_switch_do_mdb_add(struct dsa_switch *ds, int port,refcount_set(&a->refcount,1);list_add_tail(&a->list,&dp->mdbs);-return0;+out:+mutex_unlock(&dp->addr_lists_lock);++returnerr;}staticintdsa_switch_do_mdb_del(structdsa_switch*ds,intport,
@@ -249,29 +256,36 @@ static int dsa_switch_do_mdb_del(struct dsa_switch *ds, int port,{structdsa_port*dp=dsa_to_port(ds,port);structdsa_mac_addr*a;-interr;+interr=0;/* No need to bother with refcounting for user ports */if(!(dsa_port_is_cpu(dp)||dsa_port_is_dsa(dp)))returnds->ops->port_mdb_del(ds,port,mdb);+mutex_lock(&dp->addr_lists_lock);+a=dsa_mac_addr_find(&dp->mdbs,mdb->addr,mdb->vid);-if(!a)-return-ENOENT;+if(!a){+err=-ENOENT;+gotoout;+}if(!refcount_dec_and_test(&a->refcount))-return0;+gotoout;err=ds->ops->port_mdb_del(ds,port,mdb);if(err){refcount_inc(&a->refcount);-returnerr;+gotoout;}list_del(&a->list);kfree(a);-return0;+out:+mutex_unlock(&dp->addr_lists_lock);++returnerr;}staticintdsa_switch_do_fdb_add(structdsa_switch*ds,intport,
@@ -279,26 +293,30 @@ static int dsa_switch_do_fdb_add(struct dsa_switch *ds, int port,{structdsa_port*dp=dsa_to_port(ds,port);structdsa_mac_addr*a;-interr;+interr=0;/* No need to bother with refcounting for user ports */if(!(dsa_port_is_cpu(dp)||dsa_port_is_dsa(dp)))returnds->ops->port_fdb_add(ds,port,addr,vid);+mutex_lock(&dp->addr_lists_lock);+a=dsa_mac_addr_find(&dp->fdbs,addr,vid);if(a){refcount_inc(&a->refcount);-return0;+gotoout;}a=kzalloc(sizeof(*a),GFP_KERNEL);-if(!a)-return-ENOMEM;+if(!a){+err=-ENOMEM;+gotoout;+}err=ds->ops->port_fdb_add(ds,port,addr,vid);if(err){kfree(a);-returnerr;+gotoout;}ether_addr_copy(a->addr,addr);
@@ -306,7 +324,10 @@ static int dsa_switch_do_fdb_add(struct dsa_switch *ds, int port,refcount_set(&a->refcount,1);list_add_tail(&a->list,&dp->fdbs);-return0;+out:+mutex_unlock(&dp->addr_lists_lock);++returnerr;}staticintdsa_switch_do_fdb_del(structdsa_switch*ds,intport,
@@ -314,29 +335,36 @@ static int dsa_switch_do_fdb_del(struct dsa_switch *ds, int port,{structdsa_port*dp=dsa_to_port(ds,port);structdsa_mac_addr*a;-interr;+interr=0;/* No need to bother with refcounting for user ports */if(!(dsa_port_is_cpu(dp)||dsa_port_is_dsa(dp)))returnds->ops->port_fdb_del(ds,port,addr,vid);+mutex_lock(&dp->addr_lists_lock);+a=dsa_mac_addr_find(&dp->fdbs,addr,vid);-if(!a)-return-ENOENT;+if(!a){+err=-ENOENT;+gotoout;+}if(!refcount_dec_and_test(&a->refcount))-return0;+gotoout;err=ds->ops->port_fdb_del(ds,port,addr,vid);if(err){refcount_inc(&a->refcount);-returnerr;+gotoout;}list_del(&a->list);kfree(a);-return0;+out:+mutex_unlock(&dp->addr_lists_lock);++returnerr;}staticintdsa_switch_host_fdb_add(structdsa_switch*ds,
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:41
DSA would like to remove the rtnl_lock from its
SWITCHDEV_FDB_{ADD,DEL}_TO_DEVICE handlers, and the felix driver uses
the same MAC table functions as ocelot.
This means that the MAC table functions will no longer be implicitly
serialized with respect to each other by the rtnl_mutex, we need to add
a dedicated lock in ocelot for the non-atomic operations of selecting a
MAC table row, reading/writing what we want and polling for completion.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
drivers/net/ethernet/mscc/ocelot.c | 53 +++++++++++++++++++++++-------
include/soc/mscc/ocelot.h | 3 ++
2 files changed, 44 insertions(+), 12 deletions(-)
@@ -20,11 +20,13 @@ struct ocelot_mact_entry {enummacaccess_entry_typetype;};+/* Must be called with &ocelot->mact_lock held */staticinlineu32ocelot_mact_read_macaccess(structocelot*ocelot){returnocelot_read(ocelot,ANA_TABLES_MACACCESS);}+/* Must be called with &ocelot->mact_lock held */staticinlineintocelot_mact_wait_for_completion(structocelot*ocelot){u32val;
@@ -36,6 +38,7 @@ static inline int ocelot_mact_wait_for_completion(struct ocelot *ocelot)TABLE_UPDATE_SLEEP_US,TABLE_UPDATE_TIMEOUT_US);}+/* Must be called with &ocelot->mact_lock held */staticvoidocelot_mact_select(structocelot*ocelot,constunsignedcharmac[ETH_ALEN],unsignedintvid)
@@ -67,6 +70,7 @@ int ocelot_mact_learn(struct ocelot *ocelot, int port,ANA_TABLES_MACACCESS_ENTRYTYPE(type)|ANA_TABLES_MACACCESS_MAC_TABLE_CMD(MACACCESS_CMD_LEARN);unsignedintmc_ports;+interr;/* Set MAC_CPU_COPY if the CPU port is used by a multicast entry */if(type==ENTRYTYPE_MACv4)
@@ -79,18 +83,28 @@ int ocelot_mact_learn(struct ocelot *ocelot, int port,if(mc_ports&BIT(ocelot->num_phys_ports))cmd|=ANA_TABLES_MACACCESS_MAC_CPU_COPY;+mutex_lock(&ocelot->mact_lock);+ocelot_mact_select(ocelot,mac,vid);/* Issue a write command */ocelot_write(ocelot,cmd,ANA_TABLES_MACACCESS);-returnocelot_mact_wait_for_completion(ocelot);+err=ocelot_mact_wait_for_completion(ocelot);++mutex_unlock(&ocelot->mact_lock);++returnerr;}EXPORT_SYMBOL(ocelot_mact_learn);intocelot_mact_forget(structocelot*ocelot,constunsignedcharmac[ETH_ALEN],unsignedintvid){+interr;++mutex_lock(&ocelot->mact_lock);+ocelot_mact_select(ocelot,mac,vid);/* Issue a forget command */
@@ -98,7 +112,11 @@ int ocelot_mact_forget(struct ocelot *ocelot,ANA_TABLES_MACACCESS_MAC_TABLE_CMD(MACACCESS_CMD_FORGET),ANA_TABLES_MACACCESS);-returnocelot_mact_wait_for_completion(ocelot);+err=ocelot_mact_wait_for_completion(ocelot);++mutex_unlock(&ocelot->mact_lock);++returnerr;}EXPORT_SYMBOL(ocelot_mact_forget);
@@ -114,7 +132,9 @@ static void ocelot_mact_init(struct ocelot *ocelot)|ANA_AGENCTRL_LEARN_IGNORE_VLAN,ANA_AGENCTRL);-/* Clear the MAC table */+/* Clear the MAC table. We are not concurrent with anyone, so+*holding&ocelot->mact_lockispointless.+*/ocelot_write(ocelot,MACACCESS_CMD_INIT,ANA_TABLES_MACACCESS);}
@@ -1028,6 +1048,7 @@ int ocelot_port_fdb_do_dump(const unsigned char *addr, u16 vid,}EXPORT_SYMBOL(ocelot_port_fdb_do_dump);+/* Must be called with &ocelot->mact_lock held */staticintocelot_mact_read(structocelot*ocelot,intport,introw,intcol,structocelot_mact_entry*entry){
@@ -1078,33 +1099,40 @@ static int ocelot_mact_read(struct ocelot *ocelot, int port, int row, int col,intocelot_fdb_dump(structocelot*ocelot,intport,dsa_fdb_dump_cb_t*cb,void*data){+interr=0;inti,j;+/* We could take the lock just around ocelot_mact_read, but doing so+*thousandsoftimesinarowseemsratherpointlessandinefficient.+*/+mutex_lock(&ocelot->mact_lock);+/* Loop through all the mac tables entries. */for(i=0;i<ocelot->num_mact_rows;i++){for(j=0;j<4;j++){structocelot_mact_entryentry;boolis_static;-intret;-ret=ocelot_mact_read(ocelot,port,i,j,&entry);+err=ocelot_mact_read(ocelot,port,i,j,&entry);/* If the entry is invalid (wrong port, invalid...),*skipit.*/-if(ret==-EINVAL)+if(err==-EINVAL)continue;-elseif(ret)-returnret;+elseif(err)+break;is_static=(entry.type==ENTRYTYPE_LOCKED);-ret=cb(entry.mac,entry.vid,is_static,data);-if(ret)-returnret;+err=cb(entry.mac,entry.vid,is_static,data);+if(err)+break;}}-return0;+mutex_unlock(&ocelot->mact_lock);++returnerr;}EXPORT_SYMBOL(ocelot_fdb_dump);
@@ -2085,6 +2113,7 @@ int ocelot_init(struct ocelot *ocelot)mutex_init(&ocelot->stats_lock);mutex_init(&ocelot->ptp_lock);+mutex_init(&ocelot->mact_lock);spin_lock_init(&ocelot->ptp_clock_lock);snprintf(queue_name,sizeof(queue_name),"%s-stats",dev_name(ocelot->dev));
@@ -674,6 +674,9 @@ struct ocelot {structdelayed_workstats_work;structworkqueue_struct*stats_queue;+/* Lock for serializing access to the MAC table */+structmutexmact_lock;+structworkqueue_struct*owq;u8ptp:1;
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:42
After talking with Ido Schimmel, it became clear that rtnl_lock is not
actually required for anything that is done inside the
SWITCHDEV_FDB_{ADD,DEL}_TO_DEVICE deferred work handlers.
The reason why it was probably added by Arkadi Sharshevsky in commit
c9eb3e0f8701 ("net: dsa: Add support for learning FDB through
notification") was to offer the same locking/serialization guarantees as
.ndo_fdb_{add,del} and avoid reworking any drivers.
DSA has implemented .ndo_fdb_add and .ndo_fdb_del until commit
b117e1e8a86d ("net: dsa: delete dsa_legacy_fdb_add and
dsa_legacy_fdb_del") - that is to say, until fairly recently.
But those methods have been deleted, so now we are free to drop the
rtnl_lock as well.
Note that exposing DSA switch drivers to an unlocked method which was
previously serialized by the rtnl_mutex is a potentially dangerous
affair. Driver writers couldn't ensure that their internal locking
scheme does the right thing even if they wanted.
We could err on the side of paranoia and introduce a switch-wide lock
inside the DSA framework, but that seems way overreaching. Instead, we
could check as many drivers for regressions as we can, fix those first,
then let this change go in once it is assumed to be fairly safe.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
net/dsa/slave.c | 2 --
1 file changed, 2 deletions(-)
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:44
DSA is preparing to offer switch drivers an API through which they can
associate each FDB entry with a struct net_device *bridge_dev. This can
be used to perform FDB isolation (the FDB lookup performed on the
ingress of a standalone, or bridged port, should not find an FDB entry
that is present in the FDB of another bridge).
In preparation of that work, DSA needs to ensure that by the time we
call the switch .port_fdb_add and .port_fdb_del methods, the
dp->bridge_dev pointer is still valid, i.e. the port is still a bridge
port.
Currently this is true for .port_fdb_add, but not guaranteed to be true
for .port_fdb_del. This is because the SWITCHDEV_FDB_{ADD,DEL}_TO_DEVICE
API requires drivers that must have sleepable context to handle those
events to schedule the deferred work themselves. DSA does this through
the dsa_owq.
It can happen that a port leaves a bridge, del_nbp() flushes the FDB on
that port, SWITCHDEV_FDB_DEL_TO_DEVICE is notified in atomic context,
DSA schedules its deferred work, but del_nbp() finishes unlinking the
bridge as a master from the port before DSA's deferred work is run.
Fundamentally, the port must not be unlinked from the bridge until all
FDB deletion deferred work items have been flushed. The bridge must wait
for the completion of these hardware accesses.
I have tried to address this issue centrally in switchdev by making
SWITCHDEV_FDB_DEL_TO_DEVICE deferred (=> blocking) at the switchdev
level, which would offer implicit synchronization with del_nbp:
https://patchwork.kernel.org/project/netdevbpf/cover/20210820115746.3701811-1-vladimir.oltean@nxp.com/
but it seems that any attempt to modify switchdev's behavior and make
the events blocking there would introduce undesirable side effects in
other switchdev consumers.
The most undesirable behavior seems to be that
switchdev_deferred_process_work() takes the rtnl_mutex itself, which
would be worse off than having the rtnl_mutex taken individually from
drivers which is what we have now.
So to offer the needed guarantee to DSA switch drivers, I have come up
with a compromise solution that does not require switchdev rework:
we already have a hook at the last moment in time when the bridge is
still an upper of ours: the NETDEV_PRECHANGEUPPER handler. We can flush
the dsa_owq manually from there, which makes all FDB deletions
synchronous.
Major problem: the NETDEV_PRECHANGEUPPER event runs with rtnl_mutex held,
so flushing dsa_owq would deadlock if dsa_slave_switchdev_event_work
would take the rtnl_mutex too.
So not only would it be desirable to drop the rtnl_lock from DSA, it is
actually mandatory to do so.
This change requires ACKs from driver maintainers, since we expose
switches to a method which is now unlocked and can trigger concurrency
issue in the access to hardware.
I've eyeballed the existing drivers, and have needed to patch sja1105
and felix/ocelot. I am also looking at the b53 driver where the ARL ops
are unlocked. The other drivers do seem to have a mutex of sorts, but I
am fairly skeptical that its serialization features have really been put
to the test (knowing that the rtnl_mutex serialized accesses already).
So any regression test from drivers that implement:
- .port_fdb_add
- .port_fdb_del
- .port_fdb_dump
- .port_mdb_add
- .port_mdb_del
- .port_fast_age
is appreciated.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
net/dsa/dsa.c | 5 +++++
net/dsa/dsa_priv.h | 2 ++
net/dsa/port.c | 2 ++
3 files changed, 9 insertions(+)
From: Vladimir Oltean <vladimir.oltean@nxp.com> Date: 2021-08-24 11:41:47
These programs are useful, but not all selftests require them.
Additionally, on embedded boards without package management (things like
buildroot), installing mausezahn or jq is not always as trivial as
downloading a package from the web.
So it is actually a bit annoying to require programs that are not used.
Introduce options that can be set by scripts to not enforce these
dependencies. For compatibility, default to "yes".
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
tools/testing/selftests/net/forwarding/lib.sh | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
@@ -138,8 +140,12 @@ require_command()fi}-require_commandjq-require_command$MZ+if[["$REQUIRE_JQ"="yes"]];then+require_commandjq+fi+if[["$REQUIRE_MZ"="yes"]];then+require_command$MZ+fiif[[!-vNUM_NETIFS]];thenecho"SKIP: importer does not define \"NUM_NETIFS\""