We use Ganesha 2.3.0 NFS server in our filesystem, and in a use-case, the
status of Ganesha and rpcbind ended up as follows. Note that only Ganesha
is using rpcbind, RQUOTA port.
- Ganesha is refusing to start
> 03/03/2016 T13:41:25.368197-0800 : nfs-ganesha-16909[main] 335
> :Bind_sockets_V6 :D
>From Dominique Martinet :
Dominique Martinet has uploaded a new change for review.
https://review.gerrithub.io/265120
Change subject: SAL/nfs4_clientid: don't create records with empty client_val
..
SAL/nfs4_clientid: don't
>From Dominique Martinet :
Dominique Martinet has uploaded a new change for review.
https://review.gerrithub.io/265121
Change subject: nfs4 layoutreturn: don't access layout_state on reclaim
..
nfs4 layoutreturn: don't access
>From Dominique Martinet :
Dominique Martinet has uploaded a new change for review.
https://review.gerrithub.io/265122
Change subject: nfs_proto_tools: fix Fattr handling:
..
nfs_proto_tools: fix Fattr handling:
- need to m
> -Original Message-
> From: Dominique Martinet [mailto:dominique.marti...@cea.fr]
> Sent: Thursday, March 3, 2016 12:46 PM
> To: Frank Filz
> Cc: 'William Allen Simpson' ; nfs-
> ganesha-de...@lists.sourceforge.net
> Subject: Re: [Nfs-ganesha-devel] Unbounded memory allocations (based o
Hi,
got this for inline_xdr_string:
- I don't get why strlen is called on FREE, we don't need size to
actually be set for it and if it's a free after a decode that failed
(e.g. hit maxlen) then the pointer is not valid
- hence don't trust size for op FREE and early bailout. That's what the
other
Frank Filz wrote on Wed, Mar 02, 2016 at 05:01:52PM -0800:
> > - all arrays are 1k
>
> Are we sure 1k is enough for all arrays?
Couldn't see any array that'd need more.
I was thinking readdir results could be, but it's a single opaque so
it's fine... But please double-check.
>> - all xdr_byte
