<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, May 19, 2014 at 8:39 AM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The 32 limit you are hitting is caused by FUSE. The Linux kernel module<br>
provides the groups of the process that accesses the FUSE-mountpoint<br>
through /proc/$PID/status (line starting with 'Groups:'). The kernel<br>
does not pass more groups than 32, this limit is hardcoded in the FUSE<br>
kernel module.<br></blockquote><div><br></div><div>Minor nit - 32 groupid limit is independent of FUSE. It is just the limited number of groupIDs the kernel exposes through proc. FUSE filesystems's only option is to use this sub-optimal interface to get group IDs. It is not unreasonable to actually implement a new reverse call in FUSE over /dev/fuse to resolve group-ids of a given request/process. Even then, the 400byte RPC limit of 93 would apply (we could at some point in the future move away from RPC)</div>
<div><br></div><div>Avati</div></div></div></div>