>From Jeff Layton :
Jeff Layton has uploaded this change for review. (
https://review.gerrithub.io/377237
Change subject: nfs: fix cleanup after delegrecall
..
nfs: fix cleanup after delegrecall
It wasn't releasing the slot p
>From Jeff Layton :
Jeff Layton has uploaded this change for review. (
https://review.gerrithub.io/377236
Change subject: nfs: nfs41_complete_single -> nfs41_release_single
..
nfs: nfs41_complete_single -> nfs41_release_single
>From Frank Filz :
Frank Filz has uploaded this change for review. (
https://review.gerrithub.io/377219
Change subject: FSAL_RGW: Remove obsolete (non-support_ex) create method
..
FSAL_RGW: Remove obsolete (non-support_ex) cre
>From Malahal :
Malahal has uploaded this change for review. (
https://review.gerrithub.io/377205
Change subject: Fix sleep path for debian
..
Fix sleep path for debian
Debian systems have it at /bin/sleep
Change-Id: I859165
>From Malahal :
Malahal has uploaded this change for review. (
https://review.gerrithub.io/377206
Change subject: Fix rpc-statd.service path on debian
..
Fix rpc-statd.service path on debian
Created nfs-ganesha-lock.service.d
I'm stumped, then. It all looks fine to me.
Daniel
On 09/05/2017 10:25 AM, Madhu P Punjabi wrote:
Hi Daniel,
Please find the response to your question "What it at 0x7fcabc550688"in
the mail below. Thank you.
Regards,
Madhu.
Inactive hide details for Daniel Gryniewicz ---09/05/2017 06:53:1
Hi Daniel,
Please find the response to your question "What it at 0x7fcabc550688" in
the mail below. Thank you.
Regards,
Madhu.
From: Daniel Gryniewicz
To: nfs-ganesha-devel@lists.sourceforge.net
Date: 09/05/2017 06:53 PM
Subject:Re: [Nfs-ganesha-devel] Segfault seen in libnti
On 09/04/2017 03:52 AM, Madhu P Punjabi wrote:
Hi All,
We have a customer who has reported a segfault in libntirpc code, when
using ganesha 2.3 on CentOS 7.
Looking at the customer's coredump below, it was not clear why a
segfault was seen even though the values (and addresses) passed to the
Can you pinpoint the line in your code? In mine, it's a warnx, and the
only jump should be using initialized data.
Daniel
On 09/01/2017 03:39 PM, Malahal Naineni wrote:
Hopefully, it fixes this valgrind warning I just got:
==17120== Thread 13:
==17120== Conditional jump or move depends on un
On Tue, 2017-09-05 at 05:41 -0400, William Allen Simpson wrote:
> On 9/4/17 6:59 AM, Swen Schillig wrote:
> > On Sat, 2017-09-02 at 00:15 -0400, William Allen Simpson wrote:
> > > On 9/1/17 6:09 PM, Frank Filz wrote:
> > > > Lately, we have been plagued by a lot of intermittent test
> > > > failure
On 9/4/17 6:59 AM, Swen Schillig wrote:
On Sat, 2017-09-02 at 00:15 -0400, William Allen Simpson wrote:
On 9/1/17 6:09 PM, Frank Filz wrote:
Lately, we have been plagued by a lot of intermittent test
failures.
I have seen intermittent failures in pynfs WRT14, WRT15, and WRT16.
These
have not b
>From Swen Schillig :
Swen Schillig has uploaded this change for review. (
https://review.gerrithub.io/377136
Change subject: setclientid: free clientid if client_r_addr is too long.
..
setclientid: free clientid if client_r_a
>From Malahal :
Malahal has uploaded this change for review. (
https://review.gerrithub.io/377128
Change subject: Fix Dispatch_Max_Reqs max value in documentation.
..
Fix Dispatch_Max_Reqs max value in documentation.
The code
13 matches
Mail list logo
