2. What is the nature and description of the request?

The customer has observed that 'ld' can sometimes cause the system to spend a
large amount of time and resources (to the point of preventing any
interactivity with the system) while generating the Build ID. This happens in
particular on systems with a large amount of memory when compiling programs
with a large (but not larger than available memory) .bss section.

This request is to add logic to ld to check for this scenario and either avoid
it or print a warning.


3. Why does the customer need this? (List the business requirements here)

There is no specific business impact to the customer; he knows how to avoid the
problem that this solves. However, he feels it would be of potential benefit to
other users to have this functionality implemented.


4. How would the customer like to achieve this? (List the functional
requirements here)

This only applies when --build-id is not explicitly set. ld would attempt to
detect when generating the sha1sum for the Build ID would take a long time and
be very resource-intensive. It would then either:

4a. Abort the linking and require passing an explicit option to continue
(either setting --build-id explicitly or passing an option such as
--force-build-id)

4b. Leave the .bss section out of the Build ID computation. This has the
advantage of being easier to detect in code - we could simply hard-code a
threshold size for the .bss section, and if it exceeds this size, do not
include in it the sha1sum input.

4c. Continue normally, but print a warning that the compilation may cause
hangs/performance issues/take a long time. Include information about overriding
with --build-id in this warning.


5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.

A test program that creates an arbitrarily-sized bss section is already
attached to the ticket. We could use this program to confirm that the behavior
is triggered under the right circumstances. Additionally, the customer could
verify that his machine no longer experiences hangs when compiling without the
--build-id option.


6. Is there already an existing RFE upstream or in Red Hat bugzilla?

No.


7. How quickly does this need resolved? (desired target release)

No specific release is desired; this is simply something the customer considers
a good idea, and he has an indefinite workaround (--build-id=none)


8. Does this request meet the RHEL Inclusion criteria (please review)

Yes, for either a major or a minor release.


9. List the affected packages

binutils


10. Would the customer be able to assist in testing this functionality if implemented?

Yes