[Bug ports/16372] New: tst-longjmp_chk2 fails on ia64 due to missing sigaltstack checking

[Bug ports/16372] New: tst-longjmp_chk2 fails on ia64 due to missing sigaltstack checking

[vapier at gentoo dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=16372

            Bug ID: 16372
           Summary: tst-longjmp_chk2 fails on ia64 due to missing
                    sigaltstack checking
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ports
          Assignee: vapier at gentoo dot org
          Reporter: vapier at gentoo dot org
                CC: carlos at redhat dot com, roland at gnu dot org
              Host: ia64-linux-gnu

the tst-longjmp_chk2 test case has been failing on ia64 since it was added. 
it's to make sure that the longjmp logic works with signal stacks in addition
to the main stacks.  ports/sysdeps/unix/sysv/linux/ia64/____longjmp_chk.S
doesn't consult sigaltstack and the test fails.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug ports/16372] tst-longjmp_chk2 fails on ia64 due to missing sigaltstack checking

[cvs-commit at gcc dot gnu.org]

http://sourceware.org/bugzilla/show_bug.cgi?id=16372

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  98b78b4b72131264b1950edbcd94287041ec8311 (commit)
      from  e646a161cef3069fe1a6c92b750a87350630c62d (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=98b78b4b72131264b1950edbcd94287041ec8311

commit 98b78b4b72131264b1950edbcd94287041ec8311
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sun Dec 29 21:16:25 2013 +0000

    ia64: longjmp_chk: support signal stacks [BZ #16372]

    The sp check has to be moved up to the start of the func since it now
    makes a system call and that'll clobber a lot of registers.

    URL: https://sourceware.org/bugzilla/show_bug.cgi?id=16372
    Signed-off-by: Mike Frysinger <vapier@gentoo.org>

-----------------------------------------------------------------------

Summary of changes:
 NEWS                                               |    2 +-
 ports/ChangeLog.ia64                               |   11 ++++
 ports/sysdeps/unix/sysv/linux/ia64/Makefile        |    1 +
 .../sysdeps/unix/sysv/linux/ia64/____longjmp_chk.S |   61 +++++++++++++++++--
 ports/sysdeps/unix/sysv/linux/ia64/__longjmp.S     |    8 +--
 .../unix/sysv/linux/ia64}/sigaltstack-offsets.sym  |    0
 6 files changed, 70 insertions(+), 13 deletions(-)
 copy {sysdeps/unix/sysv/linux/sh =>
ports/sysdeps/unix/sysv/linux/ia64}/sigaltstack-offsets.sym (100%)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug ports/16372] tst-longjmp_chk2 fails on ia64 due to missing sigaltstack checking

[vapier at gentoo dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=16372

Mike Frysinger <vapier at gentoo dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
            Version|unspecified                 |2.19
         Resolution|---                         |FIXED

--- Comment #2 from Mike Frysinger <vapier at gentoo dot org> ---
should be fixed now

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug ports/16372] tst-longjmp_chk2 fails on ia64 due to missing sigaltstack checking

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16372

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.