Date: Sun, 24 Dec 2017 02:06:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224371] vxlan leaks memory Message-ID: <bug-224371-2472-neiAdruH3G@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224371-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-224371-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224371 --- Comment #2 from commit-hook@freebsd.org --- A commit references this bug: Author: ae Date: Sun Dec 24 02:05:19 UTC 2017 New revision: 327141 URL: https://svnweb.freebsd.org/changeset/base/327141 Log: MFC r326898: Fix possible memory leak. vxlan_ftable entries are sorted in descending order, due to wrong argum= ents order it is possible to stop search before existing element will be fou= nd. Then new element will be allocated in vxlan_ftable_update_locked() and = can be inserted in the list second time or trigger MPASS() assertion with enabled INVARIANTS. PR: 224371 Changes: _U stable/11/ stable/11/sys/net/if_vxlan.c --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224371-2472-neiAdruH3G>