http://bugzilla.suse.com/show_bug.cgi?id=1165351 http://bugzilla.suse.com/show_bug.cgi?id=1165351#c31 --- Comment #31 from Luis Chamberlain <luis.chamberlain@suse.com> --- (In reply to Luis Chamberlain from comment #27)
(In reply to Franck Bui from comment #25)
(In reply to Luis Chamberlain from comment #23)
Also, if the culprit is libtirpc function __rpc_dtbsize() shouldn't we be able to proof of concept this easily? And wouldn't this issue be more visible and easier to reproduce elsewhere?
See previous comments, it's due to the fact __rpc_dtbsize() is called with rlimits inherited from PID1.
OK.
The rlimits of started service are initialized *after* the call to initgroups(3).
Are you saying that there is a race between the use of __rpc_dtbsize() and its initialized values?
What explains that this is not reproducible on a twin system, with the same software?
This goes unanswered. Why is this only occurring on *some* systems, not all? Why can we not easily reproduce with other test cases with 100% certainty? Also, is there a work around I can use in the meantime, to move on with life in the meantime with this system? -- You are receiving this mail because: You are on the CC list for the bug.