Bug 195668 - No more syscallN, update documentation
Summary: No more syscallN, update documentation
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: man-pages
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-16 14:08 UTC by Nurdin Premji
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-07-24 09:03:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nurdin Premji 2006-06-16 14:08:29 UTC
Description of problem:

In previous linux releases, the macro syscall0, syscall1, ... were all available
(defined in linux/unistd.h from memory) for use when declaring non-standard
system call interfaces such as tkill et.l.

In FC-6 that is no longer available, instead syscall(2) should be used.
The documentation should be updated to reflect this.

Comment 1 Jakub Jelinek 2006-06-16 14:13:22 UTC
This has nothing to do with glibc, the change was done in glibc-kernheaders
and documentation is in man-pages.

Comment 2 David Woodhouse 2006-06-16 14:26:53 UTC
The syscallX macros in the kernel's private headers were never suitable for
userspace. For a while, we used to _add_ something in linux/unistd.h which just
used glibc's syscall(2). But that was a bad plan -- userspace should not be
using kernel headers, and adding stuff to kernel-private headers _solely_ for
userspace isn't something we're likely to get away with upstream.

Either we could add syscallX macros to glibc's headers, or we should fix the
man-pages to document the use of syscall(2) instead. Or both. 

Comment 3 Stepan Kasal 2007-06-20 17:42:52 UTC
As noted in bug #235206, man-pages-2.55 fixes this.
(There is one possible omission, intro.2, though.)

Comment 4 Stepan Kasal 2007-07-24 09:03:15 UTC
As noted in comment #8 for bug #235206, version 2.61 fixed the problems in
intro(2), and even updated the obsolete setup(2).
To conclude, current build contains a complete fix.


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