@ Raghavendra. The io threads stack wind/ unwind may be the reason
This is what the stack looked like when it hit the mprotect guarded page. I
am not sure why there are so few frames..
but the register values did match to the guarded address. so we know stack
was being overused.
(gdb) where
#0 0x0
Hi Sanoj,
Do you testing with changing the 16K to 2M (default stack size)?
If also overflowing, there must be an important issue exist;
not overflowing, only the issue of 16K is small for marker without io-threads?
thanks,
Kinglong Mee
On 6/28/2017 19:48, Sanoj Unnikrishnan wrote:
> Hi Kinglong
- Original Message -
> From: "Sanoj Unnikrishnan"
> To: "Kinglong Mee"
> Cc: "Gluster Devel"
> Sent: Wednesday, June 28, 2017 5:18:56 PM
> Subject: Re: [Gluster-devel] glusterfsd crash when using quota without
>
Hi Kinglong,
I opened https://bugzilla.redhat.com/show_bug.cgi?id=1465861 to track this.
It seems to be an important issue that went undetected.
Thanks for catching this!!
In my attempts to repro this , I found that on each run some random
structures where getting corrupted and running into segfa
Hi Kinglong
I was reading about makecontext/swapcontext as well,
I did find an article that suggested to use mprotect and force a segfault
to check if we have a stack space issue here.
here is the link. http://www.evanjones.ca/software/threading.html.
I don't think i can try this until tomorrow.
t
Hi Sanoj,
What's your opinion about this problem?
thanks,
Kinglong Mee
On 6/9/2017 17:20, Kinglong Mee wrote:
> Hi Sanoj,
>
> On 6/9/2017 15:48, Sanoj Unnikrishnan wrote:
>> I have not used valgrind before, so I may be wrong here.
>>
>> I think the valgrind_stack_deregister should have been aft
I have not used valgrind before, so I may be wrong here.
I think the valgrind_stack_deregister should have been after GF_FREE_STACK.
That may explain the instance of invalid_write during stack_destroy calls
in after.log.
There seems to be numerous issues reported in before.log (I am assuming,
you
I would still be worried about the Invalid read/write. IMO whether an
illegal access causes a crash depends on whether the page is currently
mapped.
So, it could so happen that there is a use after free / use outside of
bounds happening in the code and it turns out that this location gets
mapped
After deleting io-threads from the vols, quota operates (list/set/modify) lets
glusterfsd crash.
I use it at CentOS 7 (CentOS Linux release 7.3.1611) with glusterfs 3.8.12.
It seems the stack corrupt, when testing with the following diff, glusterfsd
runs correctly.
There are two questions as,
1.
