diff options
author | Tobin C. Harding <tobin@kernel.org> | 2019-05-10 12:52:12 +1000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-16 19:42:33 +0200 |
commit | 100b03e87149401d9499b7579becf76140239654 (patch) | |
tree | ace673b5f265112521e7f188ce1f8b7f20213191 /lib/test_kmod.c | |
parent | 1c9adbae111e86fd97b4d7a6ed24ccfaf4ceb694 (diff) | |
download | linux-stable-100b03e87149401d9499b7579becf76140239654.tar.gz linux-stable-100b03e87149401d9499b7579becf76140239654.tar.bz2 linux-stable-100b03e87149401d9499b7579becf76140239654.zip |
bridge: Fix error path for kobject_init_and_add()
[ Upstream commit bdfad5aec1392b93495b77b864d58d7f101dc1c1 ]
Currently error return from kobject_init_and_add() is not followed by a
call to kobject_put(). This means there is a memory leak. We currently
set p to NULL so that kfree() may be called on it as a noop, the code is
arguably clearer if we move the kfree() up closer to where it is
called (instead of after goto jump).
Remove a goto label 'err1' and jump to call to kobject_put() in error
return from kobject_init_and_add() fixing the memory leak. Re-name goto
label 'put_back' to 'err1' now that we don't use err1, following current
nomenclature (err1, err2 ...). Move call to kfree out of the error
code at bottom of function up to closer to where memory was allocated.
Add comment to clarify call to kfree().
Signed-off-by: Tobin C. Harding <tobin@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/test_kmod.c')
0 files changed, 0 insertions, 0 deletions