| Summary: | memrchr segfaults against zero-sized memory region | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> | ||||
| Component: | glibc | Assignee: | Andreas Schwab <schwab> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | fweimer, jakub, meyering, schwab | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | glibc-2.14.90-12.999 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-10-19 04:34:00 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Stack trace: Program received signal SIGSEGV, Segmentation fault. memrchr () at ../sysdeps/x86_64/memrchr.S:286 286 pcmpeqb (%rdi), %xmm1 (gdb) bt #0 memrchr () at ../sysdeps/x86_64/memrchr.S:286 #1 0x0000000000400889 in main () at test-memrchr.c:46 Fixed (silently) upstream: http://repo.or.cz/w/glibc.git/commit/81dcc7fb74a766f970800b9975e85b5fe7f6ea38 I backported this patch and put it into glibc f16: http://pkgs.fedoraproject.org/gitweb/?p=glibc.git;a=commitdiff;h=cf6224207fd36b9c908f7af1df1b23512b682d32 http://koji.fedoraproject.org/koji/taskinfo?taskID=3430873 The patch can be removed when f16 is next updated. WTF? Thanks for the quick fix, Rich. That bug was causing every gnulib-using package I maintain to fail the memrchr test. (In reply to comment #4) > WTF? It's so we can proceed building packages that use gnulib and run the tests. So you used the worst possible way, without consulting the package maintainer. WTF? (In reply to comment #7) > So you used the worst possible way, without consulting the package maintainer. > WTF? Could you please raise the specific problem with the patch as I did it, rather than just using general insults. glibc-2.14.90-12 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/glibc-2.14.90-12 I'm just stating the facts. Package glibc-2.14.90-12: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.14.90-12' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14337 then log in and leave karma (feedback). glibc-2.14.90-12.999 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/glibc-2.14.90-12.999 glibc-2.14.90-12.999 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 527914 [details] test-memrchr.c Description of problem: memrchr segfaults, see the attached program for a simple reproducer. Version-Release number of selected component (if applicable): glibc-2.14.90-11.x86_64 How reproducible: 100% Steps to Reproduce: 1. gcc test-memrchr.c -o test-memrchr 2. ./test-memrchr 3. Actual results: Segfault.