Return value of syscalls

• Next message: Samuel Thibault: "Re: [2.5 PATCH] bug if cpufreq driver initialization fails"
• Previous message: Martin J. Bligh: "[Bug 810] New: Kernel BUG at mm/slab.c:981"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

while debugging glibc-2.3.1 for cris-axis-linux-gnu, I encountered a
discrepancy between code and comments explaining the return value of
syscalls of the kernel (in glibc's source, architecture specific for
cris). The comment says, values between -4095 and -1 (both inclusive)
are considered to be an error. However, the code checks the return value
to be greater or equal than -4096.

I'd like to fix that. But I need to know what's wrong, the code or the
comment. So, what values indicate an error in linux's syscalls?

Best regards, Uwe

P.S.: A look in other architecture's source in glibc makes me thing the
comment is right. I just want to make sure.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Samuel Thibault: "Re: [2.5 PATCH] bug if cpufreq driver initialization fails"
• Previous message: Martin J. Bligh: "[Bug 810] New: Kernel BUG at mm/slab.c:981"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:43 EST