Andriy Gapon 497e910cd3 fstat: fix fsid comparison when executed on systems with 64-bit long
This affects only fstat on zfs and devfs, only on 64-bit systems
and only when fsid is greater than 2^31 - 1.
When fstat examines a file via stat(2) it takes uint32_t st_dev
and assigns to (signed) (64-bit) long fsid, this results in
a positive value.
When fstat examines opened files it takes int32_t f_fsid.val[0]
and assigns to (signed) (64-bit) long fsid, this results in
a negative value.
So, while initially st_dev and f_fsid.val[0] have the same bit
values they get promoted to different 64-bit values because
of the signed-vs-unsigned difference.

A fix is to use "more natural" positive numbers by introducing
intermediate unsigned cast for f_fsid.val[0].

Reviewed by:	jhb, lulf
Approved by:	re (kib)
MFC after:	1 week (to stable/7)
2009-08-20 10:57:14 +00:00
..
2009-08-15 15:40:30 +00:00
2009-04-01 08:33:54 +00:00
2009-06-01 21:54:59 +00:00
2009-07-31 08:37:27 +00:00
2009-07-08 10:16:16 +00:00
2009-06-23 23:17:04 +00:00
2009-01-16 15:00:30 +00:00
2009-06-15 21:52:27 +00:00
2009-02-11 20:36:17 +00:00
2009-02-21 03:38:46 +00:00
2009-02-21 03:42:31 +00:00
2009-06-15 21:52:27 +00:00