Crud, while working on the documentation for support_ex, just came across a
method other folks implementing support_ex missed...
There is the possibility that two open2() calls to open by name will race,
resulting in two fsal_obj_handle's being created. When the MDCACHE attempts
to cache the 2nd
Branch next
Tag:V2.4.0
Release Highlights
* ntirpc V1.4.1
* cache_inode replaced with stackable FSAL_MDCACHE
* support_ex FSAL API extensions to allow associating file descriptors
or other FSAL specific information with state_t objects
* abort() on ENOMEM rather than attempt to continue
*
>From Daniel Gryniewicz :
Daniel Gryniewicz has uploaded a new change for review.
https://review.gerrithub.io/295524
Change subject: Re-add owner validation cache optimization
..
Re-add owner validation
>From :
jlay...@redhat.com has uploaded a new change for review.
https://review.gerrithub.io/295457
Change subject: ceph: fix several bugs with the USE_FSAL_CEPH_LL_LOOKUP_ROOT
..
ceph: fix several bugs
On 09/21/2016 11:09 PM, Soumya Koduri wrote:
> and another one (I lost the core) , but it was
> mdcache_lru_get->mdcache_lru_clean -> fsal_close()->close() . In
> FSAL_GLUSTER()->file_close(), below assert was hit -
>
> assert(obj_hdl->type == REGULAR_FILE);
>
> The obj_hdl->type was a large
>From Soumya :
Soumya has uploaded a new change for review.
https://review.gerrithub.io/295446
Change subject: Add gcc-c++ has Required package
..
Add gcc-c++ has Required package
With latest C++ compile