[lkml]   [1999]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Ok, making ready for pre-2.4 and code-freeze..
On Tue, 21 Dec 1999, Rogier Wolff wrote:
> On Linux at least the errno value will be set to preposterous
> values, whenever you enter the "negative" area of "kmem".

what do you mean? On Linux lseek(2) takes offset as off_t which is
signed long (on x86) but I use it all the time passing very large values
(e.g. c481ad8c which is even above 3G not 2G) to dump out data structures
belonging to modules and it works just fine i.e. memory_lseek() method
takes loff_t offsets.

what are these "preposterous values" you are talking about? lseek(2) on
large offsets in /dev/kmem does not return -1 which is what I check for
and if something does not return -1 we are not supposed to check errno.

Perhaps you meant that lseek(2) returns 0 on those offsets? errno does not
matter as 0 is not an error case.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:55    [W:0.061 / U:2.684 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site