On Mon, 2012-10-29 at 09:34 +0800, Ian Kent wrote: > > > > * Triggering the mounts simultaneously is required to reproduce the > > problem, which > > makes me think if something here (libtirpc for example) is not > > really thread safe > > or if the RPC clients must be destroyed after every use to avoid such issues. > > Don't think so, it's more likely I'm using a structure obtained from a > non-reentrant library call. Yeah, getprotobyname(3) isn't re-entrant, that's likely the problem. > > > * Another theory I wasn't able to test yet is if due to some > > build/link issue, some > > RPC functions from glibc are still being used, even when libtirpc is > > available. > > Is it possible? Could the mix cause the problem? > > Probably not since we've seen that before and it causes much more > serious problems because the opaque structure (the CLIENT) is somewhat > different. Any mix of calls should go badly wrong if that was happening. > > Ian > > > -- > To unsubscribe from this list: send the line "unsubscribe autofs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
