Re: [PATCH 03/15] sparc: Use Linux kABI for syscall return

[Florian Weimer <fw at deneb dot enyo dot de>]

* Adhemerval Zanella:

> This code seems to come from since initial git repository 
> (Linux-2.6.12-rc2).
>
> From a glibc standpoint, the error handling will be the same in fact,
> since what indicates the syscall has failed is the carry condition code
> value, not the syscall returned value ('o0' register).

The kernel will not set the carry condition code for large errors due
to the faulty check.  I think before your changes, we would not treat
these cases as errors because the carry condition is not set and we
check the separate err value.  After your changes, the carry condition
code is still not set, but the return value looks like an error return
value if unchanged, so we now treat these leaked error codes as
errors.

But I don't think this should block your changes.