From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: strange behaviour with statfs() call, looking for advice
Date: Mon, 11 Nov 2002 11:42:50 -0500 [thread overview]
Message-ID: <3DCFDE0A.1030506@nortelnetworks.com> (raw)
I seem to be getting some strange interactions between kernel space and
userspace with the statfs() call.
On an nfs-mounted but unaccessable system, the statfs() call is
returning a block count of 4294967295. Since the kernel statfs struct
has this field defined as a long and this is a 32-bit system, this is
somewhat confusing.
It turns out that the userspace headers define the "blocks" field as a
__fsblkcnt_t, which is then defined as __u_long.
What do I do? Do I cast it to a long since I know that this is what the
kernel is using?
The system in question is a yellowdog system, but the same problem is
present on a recent mandrake box as well. Is this a redhat issue?
Thanks,
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2002-11-11 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 16:42 Chris Friesen [this message]
2002-11-11 17:53 ` strange behaviour with statfs() call, looking for advice -- followup Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DCFDE0A.1030506@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox