Date: Thu, 30 Apr 2015 00:21:18 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 199671] [patch] memory leak in cam scsi Message-ID: <bug-199671-5312-Dc9yx5UNho@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-199671-5312@https.bugs.freebsd.org/bugzilla/> References: <bug-199671-5312@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=199671 Scott Long <scottl@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scottl@FreeBSD.org --- Comment #15 from Scott Long <scottl@FreeBSD.org> --- The clang static analyzer wasn't wrong. It's possible to leak the scan_info object if the conditions for the 'for' loop prevent the loop from being entered. It's not a normal occurrence in real life, but it's not impossible either. What needs to happen is that the loop increment a reference counter on scan_info, and if at the exit of the loop the refcount is 0, then free scan_info. It's not a bug in clang, and it's probably not in Coverity either, but I haven't looked at the output from that. Please don't file it as a bug with those projects. -- 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-199671-5312-Dc9yx5UNho>