[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181105.170619.795988090444501257.davem@davemloft.net>
Date: Mon, 05 Nov 2018 17:06:19 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: alexey.kodanev@...cle.com
Cc: netdev@...r.kernel.org, dsahern@...il.com
Subject: Re: [PATCH net v2 1/2] rtnetlink: restore handling of dumpit
return value in rtnl_dump_all()
From: Alexey Kodanev <alexey.kodanev@...cle.com>
Date: Fri, 2 Nov 2018 19:11:04 +0300
> For non-zero return from dumpit() we should break the loop
> in rtnl_dump_all() and return the result. Otherwise, e.g.,
> we could get the memory leak in inet6_dump_fib() [1]. The
> pointer to the allocated struct fib6_walker there (saved
> in cb->args) can be lost, reset on the next iteration.
>
> Fix it by partially restoring the previous behavior before
> commit c63586dc9b3e ("net: rtnl_dump_all needs to propagate
> error from dumpit function"). The returned error from
> dumpit() is still passed further.
...
> Fixes: c63586dc9b3e ("net: rtnl_dump_all needs to propagate error from dumpit function")
> Signed-off-by: Alexey Kodanev <alexey.kodanev@...cle.com>
Applied.
Powered by blists - more mailing lists