summaryrefslogtreecommitdiffstats
path: root/net/rose
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2017-09-28 00:41:44 +0200
committerDavid S. Miller <davem@davemloft.net>2017-09-30 16:13:31 +0100
commitfef0035c0f31322d417d1954bba5ab959bf91183 (patch)
treeafba1aec641cb4c377b0754dab9d998621dfd6fa /net/rose
parent3e7e07288e1ab8e0770f4fdbf2905e6ecf917381 (diff)
downloadlinux-fef0035c0f31322d417d1954bba5ab959bf91183.tar.gz
linux-fef0035c0f31322d417d1954bba5ab959bf91183.tar.bz2
linux-fef0035c0f31322d417d1954bba5ab959bf91183.zip
netlink: do not proceed if dump's start() errs
Drivers that use the start method for netlink dumping rely on dumpit not being called if start fails. For example, ila_xlat.c allocates memory and assigns it to cb->args[0] in its start() function. It might fail to do that and return -ENOMEM instead. However, even when returning an error, dumpit will be called, which, in the example above, quickly dereferences the memory in cb->args[0], which will OOPS the kernel. This is but one example of how this goes wrong. Since start() has always been a function with an int return type, it therefore makes sense to use it properly, rather than ignoring it. This patch thus returns early and does not call dumpit() when start() fails. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> Cc: Johannes Berg <johannes@sipsolutions.net> Reviewed-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rose')
0 files changed, 0 insertions, 0 deletions