Bug 1702828

Summary: curl segmentation fault
Product: Red Hat Enterprise Linux 7 Reporter: Paulo Andrade <pandrade>
Component: curlAssignee: Kamil Dudka <kdudka>
Status: CLOSED DUPLICATE QA Contact: Daniel Rusek <drusek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: kdudka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-25 12:14:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paulo Andrade 2019-04-24 21:20:00 UTC
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.

Comment 2 Kamil Dudka 2019-04-25 07:56:45 UTC
This looks like a duplicate of bug #1683292.  Could you please retest with curl-7.29.0-52.el7?

Comment 3 Paulo Andrade 2019-04-25 11:47:56 UTC
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.

Comment 4 Kamil Dudka 2019-04-25 12:14:52 UTC
Perfect.  Thanks for confirmation and sorry for the breakage!

*** This bug has been marked as a duplicate of bug 1683292 ***