Prev: [PATCH 5/6] futex: handle timeout inside adaptive lock spin
Next: futex: FUTEX_LOCK with optional adaptive spinning
From: Eric Dumazet on 5 Apr 2010 16:30
Hi Dave

I just noticed x86info was not working anymore on latest kernel

x86info v1.24. Dave Jones 2001-2009
Feedback to <davej(a)redhat.com>.

type seek: Value too large for defined data type


Offending syscall is an lseek(fd, -1, SEEK_CUR) on /dev/mem file



open("/dev/mem", O_RDONLY) = 3
....
lseek(3, 1023092, SEEK_SET) = 1023092
read(3, "PCMP\4\3\4\266HP PROLIANT \0\0\0\0\0"..., 44) = 44
read(3, "\0"..., 1) = 1
lseek(3, -1, SEEK_CUR) = -1 EOVERFLOW (Value too large
for defined data type)

It seems -1 is taken as an unsigned quantity ?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 5/6] futex: handle timeout inside adaptive lock spin
Next: futex: FUTEX_LOCK with optional adaptive spinning