Re: [Nfs-ganesha-devel] destroying timing window

2017-07-31 Thread Dominique Martinet
Thanks for looking at this. I apologize for the tone of that last update I posted on gerrithub as well, last week wasn't great for me and I probably spent too long on this patchset. William Allen Simpson wrote on Sun, Jul 30, 2017 at 08:54:32PM -0400: > That is, it was a superficial bandage over

Re: [Nfs-ganesha-devel] destroying timing window

2017-07-30 Thread William Allen Simpson
On 7/30/17 7:45 AM, William Allen Simpson wrote: On 7/29/17 8:46 AM, William Allen Simpson wrote: Because it will be an API change to SVC_RELEASE() -- a macro and inline function -- we cannot backport. Obviously, we haven't seen this very often. But it will be a good reason for moving downstre

Re: [Nfs-ganesha-devel] destroying timing window

2017-07-30 Thread William Allen Simpson
On 7/29/17 8:46 AM, William Allen Simpson wrote: On 7/28/17 7:37 AM, Dominique Martinet wrote: I also get a random crash with ASAN during init, one out of 3-4 times [...] I'm not able to reproduce. But Matt and I agree that you've found a race condition that has been there for a long time. I

[Nfs-ganesha-devel] destroying timing window

2017-07-29 Thread William Allen Simpson
Thought I'd share my findings and proposed solution with the whole group. On 7/28/17 7:37 AM, Dominique Martinet wrote: I also get a random crash with ASAN during init, one out of 3-4 times Here's the stack: #0 0x00507470 in __sanitizer::Die() () #1 0x004ea1be in __asan::Repor