Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Example steps to reproduce:
$ dd if=/dev/zero of=foo.txt bs=1 count=1048576
$ python -m SimpleHTTPServer &
$ curl --silent --connect-timeout 90 -w %{http_code} -g -L -e ';auto' --max-redirs 5 -C - --limit-rate 10000k -o /tmp/foo.txt.part http://127.0.0.1:8000/foo.txt -vvv
Testing on Fedora 29 it will not crash.
Testing a git bisect from curl-7_29_0 to curl-7_61_1 it turns out I cannot
reproduce it on Fedora 29, when building upstream curl-7_29_0.
Did actually a manual bisect, as need to:
$ make clean
$ rm -f /tmp/foo.txt.part
$ git checkout $tag_from_curl-7_29_0_to_curl-7_61_1
$ ./buildconf
$ make
$ LD_PRELOAD=$PWD/lib/.libs/libcurl.so ./src/.libs/curl --silent --connect-timeout 90 -w %{http_code} -g -L -e ';auto' --max-redirs 5 -C - --limit-rate 10000k -o /tmp/foo.txt.part http://127.0.0.1:8000/foo.txt -vvv
I also did omit the --with-gssapi=/usr/kerberos configure option as for some
reason it does not find the (installed) dependencies, and did not debug further.
The problem should be something in rhel7 environment, some of the rhel patches,
or a side effect of --with-gssapi.
I confirm the problem is fixed with curl-7.29.0-52.el7.
Also did check with valgrind, as my previous initial work on
bisecting it probably did not trigger due to different memory
layout. Valgrind does not show invalid memory read with the newer
package.
Example steps to reproduce: $ dd if=/dev/zero of=foo.txt bs=1 count=1048576 $ python -m SimpleHTTPServer & $ curl --silent --connect-timeout 90 -w %{http_code} -g -L -e ';auto' --max-redirs 5 -C - --limit-rate 10000k -o /tmp/foo.txt.part http://127.0.0.1:8000/foo.txt -vvv Testing on Fedora 29 it will not crash. Testing a git bisect from curl-7_29_0 to curl-7_61_1 it turns out I cannot reproduce it on Fedora 29, when building upstream curl-7_29_0. Did actually a manual bisect, as need to: $ make clean $ rm -f /tmp/foo.txt.part $ git checkout $tag_from_curl-7_29_0_to_curl-7_61_1 $ ./buildconf $ make $ LD_PRELOAD=$PWD/lib/.libs/libcurl.so ./src/.libs/curl --silent --connect-timeout 90 -w %{http_code} -g -L -e ';auto' --max-redirs 5 -C - --limit-rate 10000k -o /tmp/foo.txt.part http://127.0.0.1:8000/foo.txt -vvv I also did omit the --with-gssapi=/usr/kerberos configure option as for some reason it does not find the (installed) dependencies, and did not debug further. The problem should be something in rhel7 environment, some of the rhel patches, or a side effect of --with-gssapi.