Bug 122080 - 4G/4G patch breaks syscalls with 6 arguments
4G/4G patch breaks syscalls with 6 arguments
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Ingo Molnar
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-04-30 05:32 EDT by Jakub Jelinek
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-15 13:29:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jakub Jelinek 2004-04-30 05:32:29 EDT
i686 4G/4G sysenter vDSO handles only 5 syscalls and special-cases
mmap2.  Unfortunately, this is not the only 6 argument syscall on IA-32.
E.g. fadvise64_64 has 6 arguments too, there might be others.
I wonder if it is not possible to instead just do the get_user part
in sysenter_entry before switching page tables and deal with the possible
fault in the trap handler.
Comment 1 Jakub Jelinek 2004-04-30 05:33:44 EDT
Of course I meant "handles only 5 argument syscalls"...
Comment 2 Warren Togami 2005-05-20 05:37:53 EDT
Is this a issue for any non-i686 arch?
Since FC4 ships without 4G/4G, shouldn't this be FC5 instead of FC4 target?
Comment 3 Ingo Molnar 2005-09-15 13:29:27 EDT
closing this bug - it seems glibc is now working this around by always doing
int80 for fadvise64_64.

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