Date: Sat, 16 Dec 2017 14:37:18 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224371] vxlan leaks memory Message-ID: <bug-224371-2472-0OjdFAQAaY@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 #1 from commit-hook@freebsd.org --- A commit references this bug: Author: ae Date: Sat Dec 16 14:36:21 UTC 2017 New revision: 326898 URL: https://svnweb.freebsd.org/changeset/base/326898 Log: Fix possible memory leak. vxlan_ftable entries are sorted in ascending order, due to wrong arguments order it is possible to stop search before existing element will be found. 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 MFC after: 1 week Changes: head/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-0OjdFAQAaY>