Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1591516 - armv7: siginfo ABI regression breaks strace testsuite
Summary: armv7: siginfo ABI regression breaks strace testsuite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: armv7hl
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-14 23:52 UTC by Dmitry V. Levin
Modified: 2018-07-02 15:59 UTC (History)
19 users (show)

Fixed In Version: kernel-4.17.3-100.fc27 kernel-4.17.3-200.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-01 01:34:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dmitry V. Levin 2018-06-14 23:52:23 UTC
Upstream kernel commit v4.16-rc1~159^2~37 introduced a regression that breaks strace testsuite on armv7, see
https://marc.info/?l=linux-arm-kernel&m=152349692414229
https://koji.fedoraproject.org/koji/taskinfo?taskID=27622354
https://koji.fedoraproject.org/koji/taskinfo?taskID=27622420
https://koji.fedoraproject.org/koji/taskinfo?taskID=27622422

This bug is probably fixed by upstream kernel commit v4.17-rc1-8-g0c362f96e1c6.

New strace releases cannot be built for Fedora until the problem is fixed.

Comment 1 Laura Abbott 2018-06-15 15:27:02 UTC
The patch doesn't apply cleanly to the current 4.16 but it does apply to 4.17. We are going to be rebasing to 4.17 very soon so my preference would be to fix this when the 4.17 rebase occurs unless there is a critical need to have this fixed sooner.

Comment 2 Fedora Update System 2018-06-26 19:27:38 UTC
kernel-4.17.3-100.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2a0f8b2c9d

Comment 3 Fedora Update System 2018-06-26 19:28:56 UTC
kernel-4.17.3-200.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-d92fde52d7

Comment 4 Laura Abbott 2018-06-26 19:53:42 UTC
https://pagure.io/fedora-infrastructure/issue/7056 is tracking the upgrade of the builder vms to actually pick up the newer kernel

Comment 5 Fedora Update System 2018-06-28 12:31:26 UTC
kernel-4.17.3-100.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2a0f8b2c9d

Comment 6 Fedora Update System 2018-06-28 15:03:26 UTC
kernel-4.17.3-200.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d92fde52d7

Comment 7 Fedora Update System 2018-07-01 01:34:38 UTC
kernel-4.17.3-100.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2018-07-01 02:37:57 UTC
kernel-4.17.3-200.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Laura Abbott 2018-07-02 15:50:36 UTC
The builders have been updated with the fixed version so this should be fully fixed now.

Comment 10 Dmitry V. Levin 2018-07-02 15:59:07 UTC
Confirmed: https://koji.fedoraproject.org/koji/taskinfo?taskID=27983632
Thanks!


Note You need to log in before you can comment on or make changes to this bug.