summaryrefslogtreecommitdiffstats
path: root/Documentation/fb/tgafb.txt
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2015-05-19 15:40:21 +0200
committerJohannes Berg <johannes.berg@intel.com>2015-05-19 15:46:21 +0200
commit22d3a3c829fa9ecdb493d1f1f2838d543f8d86a3 (patch)
treed8961aabf48478add145e56acc0683fec328f9b1 /Documentation/fb/tgafb.txt
parent47b4e1fc4972cc43a19121bc2608a60aef3bf216 (diff)
downloadtalos-op-linux-22d3a3c829fa9ecdb493d1f1f2838d543f8d86a3.tar.gz
talos-op-linux-22d3a3c829fa9ecdb493d1f1f2838d543f8d86a3.zip
mac80211: don't use napi_gro_receive() outside NAPI context
No matter how the driver manages its NAPI context, there's no way sending frames to it from a timer can be correct, since it would corrupt the internal GRO lists. To avoid that, always use the non-NAPI path when releasing frames from the timer. Cc: stable@vger.kernel.org Reported-by: Jean Trivelly <jean.trivelly@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'Documentation/fb/tgafb.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud