Bug 1651010 - i686 signal handling regression
Summary: i686 signal handling regression
Keywords:
Status: CLOSED DUPLICATE of bug 1659295
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: x86Tracker
TreeView+ depends on / blocked
 
Reported: 2018-11-18 17:29 UTC by H.J. Lu
Modified: 2018-12-15 10:02 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-12-14 22:01:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 201741 0 None None None 2018-12-14 22:00:33 UTC

Description H.J. Lu 2018-11-18 17:29:41 UTC 
Under 4.19.2-300 kernel, i686 glibc tests failed with:

FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
FAIL: nptl/tst-cancel24
FAIL: nptl/tst-cancel24-static
FAIL: nptl/tst-cancelx16
FAIL: nptl/tst-cancelx18
FAIL: nptl/tst-cancelx20
FAIL: nptl/tst-cancelx21
FAIL: nptl/tst-cancelx4
FAIL: nptl/tst-cancelx5
FAIL: nptl/tst-cleanupx4
FAIL: nptl/tst-oncex3
FAIL: nptl/tst-oncex4

[hjl@gnu-skx-1 build-i686-linux]$ debug/tst-backtrace5 --direct
Obtained backtrace with 3 functions
Failure on line 53
[hjl@gnu-skx-1 build-i686-linux]$ 

Under 4.18.18-300 kernel, I got

Obtained backtrace with 7 functions
Function 0: debug/tst-backtrace5(handle_signal+0x1b) [0x804a42b]
Function 1: linux-gate.so.1(__kernel_sigreturn+0) [0xf7f7b0b0]
Function 2: linux-gate.so.1(__kernel_vsyscall+0x9) [0xf7f7b099]
Function 3: /export/build/gnu/tools-build/glibc-32bit/build-i686-linux/libc.so.6(__read+0x2d) [0xf7e99c8d]
Function 4: debug/tst-backtrace5(fn+0x105) [0x804a745]
Function 5: debug/tst-backtrace5(fn+0xd4) [0x804a714]
Function 6: debug/tst-backtrace5(fn+0xd4) [0x804a714]
Comment 1 H.J. Lu 2018-11-20 21:55:21 UTC 
This is caused by

commit 379d98ddf41344273d9718556f761420f4dc80b3
Author: Alistair Strachan <astrachan>
Date:   Fri Aug 3 10:39:31 2018 -0700

    x86: vdso: Use $LD instead of $CC to link
    
    The vdso{32,64}.so can fail to link with CC=clang when clang tries to find
    a suitable GCC toolchain to link these libraries with.
    
    /usr/bin/ld: arch/x86/entry/vdso/vclock_gettime.o:
      access beyond end of merged section (782)
Comment 2 H.J. Lu 2018-12-14 22:01:25 UTC 

*** This bug has been marked as a duplicate of bug 1659295 ***
Note You need to log in before you can comment on or make changes to this bug.