> Answer (b) breaks programs that deliberately set a limit of 0x7FFFFFFF, but
> it's less intrusive than answer (a). The patch for (b) is fairly trivial and
> I'll rustle one up if people agree it's the Right Thing.
(b) is a standards violation
> So for my purposes I can fix this by upgrading my compile host to a glibc
> that's built against 2.4.18 headers, but I still reckon there's a kernel bug
> here.
Its a compatibility bug. The original submission when it was changed did
try to address this. Originally its a kernel bug because the standards
always said that it was unsigned
-
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/
This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:18 EST