Description of problem: This problem was discovered on x86_64, but appears to be present (but not necesssecarily presenting) on all platforms. It appears that the rup utility passes data to clnt_broadcast that was allocated on the stack, but is used by the rpc callback, potentially after the allocating stack frame has itself been de-allocated. This leads to erroneous results. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.run rup with no arguments on an x86_64 RHEL3 system Actual results: rup exits with the following error: rup: RPC: Can't encode arguments Expected results: rup should print a list of responding rpc hosts. Additional info:
Created attachment 112945 [details] patch to solve stack allocation issue, by moving allocated storage to be static and global
Good catch. I'll be working on packages and erratas next week for RHEL3 U6 and RHEL4 U2. Patch looks good. Thanks, Read ya, Phil
Thanks Phil!
OK, took a week longer, but packages have been built and erratas opened and assigned to the proper update releases. Read ya, Phil
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-423.html
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-422.html