From: Stephen Hemminger <stephen@networkplumber.org>
To: Gilad Naaman <gnaaman@drivenets.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Lahav Daniel Schlesinger <lschlesinger@drivenets.com>
Subject: Re: [PATCH iproute2] libnetlink: Fix memory leak in __rtnl_talk_iov()
Date: Thu, 1 Dec 2022 08:00:24 -0800 [thread overview]
Message-ID: <20221201080024.719fe24e@hermes.local> (raw)
In-Reply-To: <D239DD38-BC1F-42BE-B854-7DED97F11D91@drivenets.com>
On Wed, 23 Nov 2022 16:15:41 +0000
Gilad Naaman <gnaaman@drivenets.com> wrote:
> If `__rtnl_talk_iov()` fails then callers are not expected to free `answer`.
>
> Currently if `NLMSG_ERROR` was received with an error then the netlink
> buffer was stored in `answer`, while still returning an error
>
> This leak can be observed by running this snippet over time.
> This triggers an `NLMSG_ERROR` because for each neighbour update, `ip`
> will try to query for the name of interface 9999 in the wrong netns.
> (which in itself is a separate bug)
>
> set -e
>
> ip netns del test-a || true
> ip netns add test-a
> ip netns del test-b || true
> ip netns add test-b
>
> ip -n test-a netns set test-b auto
> ip -n test-a link add veth_a index 9999 type veth peer name veth_b netns test-b
> ip -n test-b link set veth_b up
>
> ip -n test-a monitor link address prefix neigh nsid label all-nsid > /dev/null &
> monitor_pid=$!
> clean() {
> kill $monitor_pid
> ip netns del test-a
> ip netns del test-b
> }
> trap clean EXIT
>
> while true; do
> ip -n test-b neigh add dev veth_b 1.2.3.4 lladdr AA:AA:AA:AA:AA:AA
> ip -n test-b neigh del dev veth_b 1.2.3.4
> done
>
> Fixes: 55870df ("Improve batch and dump times by caching link lookups")
> Signed-off-by: Lahav Schlesinger <lschlesinger@drivenets.com>
> Signed-off-by: Gilad Naaman <gnaaman@drivenets.com>
> ---
> lib/libnetlink.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
The patch got mangled by MS Exchange. Please resubmit with proper formatting.
$ checkpatch.pl /tmp/leak.mbox
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#148:
If `__rtnl_talk_iov()` fails then callers are not expected to free `answer`=
WARNING: Please use correct Fixes: style 'Fixes: <12 chars of sha1> ("<title line>")' - ie: 'Fixes: 55870dfe7f8b ("Improve batch and dump times by caching link lookups")'
#186:
Fixes: 55870df ("Improve batch and dump times by caching link lookups")
ERROR: patch seems to be corrupt (line wrapped?)
#198: FILE: lib/libnetlink.c:1091:
rtnl_talk_error(h, err, errfn);
WARNING: suspect code indent for conditional statements (32, 32)
#204: FILE: lib/libnetlink.c:1093:
+ if (i < iovlen) {
free(buf);
WARNING: space prohibited between function name and open parenthesis '('
#218: FILE: lib/libnetlink.c:1102:
+ *answer =3D (struct nlmsghdr *)buf;
ERROR: spaces required around that '=' (ctx:WxV)
#218: FILE: lib/libnetlink.c:1102:
+ *answer =3D (struct nlmsghdr *)buf;
^
total: 2 errors, 4 warnings, 29 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/tmp/leak.mbox has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
next prev parent reply other threads:[~2022-12-01 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 16:15 [PATCH iproute2] libnetlink: Fix memory leak in __rtnl_talk_iov() Gilad Naaman
2022-12-01 16:00 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 8:47 Gilad Naaman
2022-12-09 18:20 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221201080024.719fe24e@hermes.local \
--to=stephen@networkplumber.org \
--cc=gnaaman@drivenets.com \
--cc=lschlesinger@drivenets.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).