Re: [PATCH net-next 3/3 v9] drivers: net: ethernet: qualcomm: rmnet: Initial implementation

In these code paths where you are the writer, you have to rely upon the RTNL mutex (or some other mutual exclusion mechanism) to protect the update operation. RCU locking itself does not provide this. So you should use something like rcu_dereference_rtnl() or similar. So this would be

Re: [PATCH net-next 3/3 v9] drivers: net: ethernet: qualcomm: rmnet: Initial implementation

From: Subash Abhinov Kasiviswanathan Date: Thu, 24 Aug 2017 22:39:26 -0600 > +static void rmnet_force_unassociate_device(struct net_device *dev) > +{ > + struct net_device *real_dev = dev; > + struct rmnet_walk_data d; > + LIST_HEAD(list); > + > + if

[PATCH net-next 3/3 v9] drivers: net: ethernet: qualcomm: rmnet: Initial implementation

RmNet driver provides a transport agnostic MAP (multiplexing and aggregation protocol) support in embedded module. Module provides virtual network devices which can be attached to any IP-mode physical device. This will be used to provide all MAP functionality on future hardware in a single