On Tue, Mar 01, 2016 at 02:54:16PM +0100, Johannes Berg wrote: > On Sun, 2016-02-28 at 20:06 -0500, Bob Copeland wrote: > > In certain cases, the 802.11 mesh pathtable code wants to > > iterate over all of the entries in the forwarding table from > > the receive path, which is inside an RCU read-side critical > > section. Enable walks inside atomic sections by allowing > > GFP_ATOMIC allocations for the walker state. > > > > Change all existing callsites to pass in GFP_KERNEL. > > Both look fine to me. > > I see you have more patches for mesh, so this probably can't go through > net-next tree directly. Yeah, these two are on top of the other mesh path table changes. So either both of these could go via mac80211-next or we could do the 1/2 in net-next and wait to apply 2/2 in mac80211-next. Whatever works for you guys. -- Bob Copeland %% http://bobcopeland.com/ -- 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
