Change Details

Rather than placing the epoch around the entire receive loop as done in r357093, only place it around the upcalls into the stack. This avoids multiple USB calls from the rtwn_rx_frame() callpath which may sleep and thus avoids a panic nowadays. Reported by: thj Reviewed by: Sponsored by: The FreeBSD Foundation Diff...:

rtwn: narrow the epoch area Rather than placing the epoch around the entire receive loop which might call into rtwn_rx_frame() and USB and sleep, split the loop into two and leave us with one unlock/lock cycle as well. Reported by: thj Suggested by: adrian Reviewed by: Sponsored by: The FreeBSD Foundation (initially) Diff...:

rtwn: narrow the epoch area Rather than placing the epoch around the entire receive loop aswhich done in r357093might call into rtwn_rx_frame() and USB and sleep, only place it aroundsplit the upcalls into the stack.loop This avoids multiple USB calls from the rtwn_rx_frame() callpath which may sleep and thus avoids a panic nowadaysinto two and leave us with one unlock/lock cycle as well. Reported by: thj Suggested by: adrian Reviewed by: Sponsored by: The FreeBSD Foundation (initially) Diff...: