On Mon, 2013-06-10 at 13:17 -0700, Thomas Pedersen wrote: > + struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh; > + u32 bit; > + > + /* if we race with running work, worst case this work becomes a noop */ > + for_each_set_bit(bit, (unsigned long *)&changed, > + sizeof(changed) * BITS_PER_BYTE) This isn't valid, it happens to work on little endian platforms but will fail on big endian 64-bit ones, because you have this in memory (0 is the lowest order nibble): 76 54 32 10 -- -- -- -- and now you point an unsigned long pointer to it, so you interpret the "--" as the lowest bits. More generally, I'd argue that mesh is being a bit odd here, flushing stations turing mesh stop can and will actually cause a BSS info update after the mesh interface has already been stopped (beaconing has been disabled in the driver.) This seems rather odd. Maybe it would be better to move the beacon update out of mesh_sta_cleanup() and into ieee80211_mesh_housekeeping() in some way? Although it'd also have to be done in the station handling in cfg.c but that shouldn't be a problem? Note also that the way you did this is rather odd, ieee80211_stop_mesh() could cause to schedule out to the workqueue for the update, but then the update won't happen. It's a bit racy though, because you could stop and restart the mesh and then the workqueue runs or something? Overall this approach seems a bit brittle? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
