Bug 108958 - MINSIGSTKSZ mismatch between ia32 and ia64
MINSIGSTKSZ mismatch between ia32 and ia64
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Baron
Brian Brock
ia32el fujitsu
Depends On:
Blocks: 107116
  Show dependency treegraph
Reported: 2003-11-03 14:27 EST by Arun Sharma
Modified: 2013-03-06 00:56 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-11 21:07:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
sigaltstk.patch (1.12 KB, patch)
2003-11-03 14:28 EST, Arun Sharma
no flags Details | Diff
Updated patch (1.16 KB, patch)
2004-01-06 21:00 EST, Arun Sharma
no flags Details | Diff

  None (edit)
Description Arun Sharma 2003-11-03 14:27:10 EST
Description of problem:

There is a MINSIGSTKSZ mismatch between ia32 and ia64 which affects
binary compatibility with ia32.

Version-Release number of selected component (if applicable):


How reproducible:

Run a ia32 program which calls sigaltstack() with a size > 2k but less
than < 128k.
Comment 1 Arun Sharma 2003-11-03 14:28:16 EST
Created attachment 95685 [details]

This patch is in both 2.4 and 2.6 base kernels.
Comment 2 Arjan van de Ven 2003-11-04 03:35:58 EST

*** This bug has been marked as a duplicate of 107116 ***
Comment 3 Arun Sharma 2004-01-06 21:00:15 EST
Created attachment 96796 [details]
Updated patch

The earlier patch didn't address the SS_DISABLE case properly.
Comment 5 Larry Troan 2004-02-23 12:06:29 EST
ISSUE TRACKER 28987 opened as sev 2
Comment 7 John Flanagan 2004-05-11 21:07:45 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


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