Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 May 2015 00:32:40 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-fs@FreeBSD.org
Subject:   [Bug 200288] Modify after Free: ZFS
Message-ID:  <bug-200288-3630-2Noiy5qsxI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200288-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-200288-3630@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=200288

Xin LI <delphij@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |delphij@FreeBSD.org

--- Comment #12 from Xin LI <delphij@FreeBSD.org> ---
(In reply to Larry Rosenman from comment #10)
I have looked at all these backtraces and they are almost identical, and
unfortunately errors like this are relatively hard to trace down, it's like
looking at dead body (assertion, which we already know where the deadly wound
is) but not a smoking gun (the code that touches freed memory).  Debugging this
can be really time consuming.

I don't know why memguard didn't catch the issue (which should), did you added
the loader.conf option:

vm.memguard.desc="solaris"

?

I *think* that the issue is probably a decreasing counter, but a quick glance
at zfs_rlock.c didn't reveal one, and the code have been there for quite a
while.

-- 
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-200288-3630-2Noiy5qsxI>