summaryrefslogtreecommitdiff
path: root/crypto/rmd128.c
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2013-06-19 08:09:57 (GMT)
committerJohannes Berg <johannes.berg@intel.com>2013-06-19 16:31:20 (GMT)
commit3a5a423bb958ad22eeccca66c533e85bf69ba10e (patch)
treeee184cabce960d6ceaf1d2ac4efd0f406c9b5555 /crypto/rmd128.c
parent795d855d56c6d172f50a974f603ba923ac93ee76 (diff)
downloadlinux-3a5a423bb958ad22eeccca66c533e85bf69ba10e.tar.xz
nl80211: fix attrbuf access race by allocating a separate one
Since my commit 3713b4e364 ("nl80211: allow splitting wiphy information in dumps"), nl80211_dump_wiphy() uses the global nl80211_fam.attrbuf for parsing the incoming data. This wouldn't be a problem if it only did so on the first dump iteration which is locked against other commands in generic netlink, but due to space constraints in cb->args (the needed state doesn't fit) I decided to always parse the original message. That's racy though since nl80211_fam.attrbuf could be used by some other parsing in generic netlink concurrently. For now, fix this by allocating a separate parse buffer (it's a bit too big for the stack, currently 1448 bytes on 64-bit). For -next, I'll change the code to parse into the global buffer in the first round only and then allocate a smaller buffer to keep the data in cb->args. Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Acked-by: David S. Miller <davem@davemloft.net> Acked-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'crypto/rmd128.c')
0 files changed, 0 insertions, 0 deletions