[Gluster-devel] Synctask memory corruption in NetBSD

Emmanuel Dreyfus manu at netbsd.org
Mon May 2 11:37:01 UTC 2016


Manikandan Selvaganesh <mselvaga at redhat.com> wrote:

> #0  0xbb4104b7 in ?? ()
> (gdb) bt
> #0  0xbb4104b7 in ?? ()
> #1  0xbb410458 in ?? ()
> #2  0x00000004 in ?? ()
> #3  0x00000006 in ?? ()
> #4  0xbb457084 in ?? ()
> #5  0xbb759119 in synctask_destroy (task=0xb8a18030) at

In my opinion there is no particular reason it should be related to
synctask: the stack is obviously corupted (0x00000004 is certainly
wrong), and we cannot trust what is below.

I do not say it cannot be in synctask, but it could be anywhere. Do you
have any hint about where the thread last executed known code?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org


More information about the Gluster-devel mailing list