From owner-freebsd-bugs Mon May 29 10:30: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B02CD37BCAD for ; Mon, 29 May 2000 10:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA58686; Mon, 29 May 2000 10:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 29 May 2000 10:30:04 -0700 (PDT) Message-Id: <200005291730.KAA58686@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Alexander Langer Subject: Re: kern/18874: 32bit NFS servers export wrong negative values to 64bit clients Reply-To: Alexander Langer Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/18874; it has been noted by GNATS. From: Alexander Langer To: Anatoly Vorobey Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/18874: 32bit NFS servers export wrong negative values to 64bit clients Date: Mon, 29 May 2000 19:21:40 +0200 Thus spake Anatoly Vorobey (mellon@pobox.com): > Gotta love those signed<-->unsigned bugs ;) Isn't that 32bit signed vs. 64bit signed? > but I don't really have a working setup with Alpha NFS to test this against. On the client, I guess? (the patch). Will it break the i386 nfs? > A brief explanation: tquad is 64-bit unsigned, and holds the available > bytes value which is really signed long. Suppose the real value is negative. > If we divide it by NFS_FABLKSIZE first, and then > cast to long, we risk turning it into a positive value by division. Yes, but what about i386, where long is only 32bit and can't hold that value? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message