From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Mogens Kjaer <mk@crc.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs client problem in kernel 2.4.0
Date: 18 Jan 2001 17:10:58 +0100 [thread overview]
Message-ID: <shsg0igvo19.fsf@charged.uio.no> (raw)
In-Reply-To: <3A6466E3.AB55716@crc.dk> <shsy9wb334a.fsf@charged.uio.no> <shsu26z32lg.fsf@charged.uio.no> <3A66E248.8A1E6A85@crc.dk>
In-Reply-To: Mogens Kjaer's message of "Thu, 18 Jan 2001 13:32:08 +0100"
>>>>> " " == Mogens Kjaer <mk@crc.dk> writes:
> This turned out to be more difficult than I thought...
> I suspect glibc-2.2-12 being the reason, but I'm not quite sure
> yet:
> The problem is, that the 64-bit dirent's are converted to
> 32-bit dirent's and a sanity check is performed, if the inodes
> or offsets don't fit into 32 bits.
> The offset of the last entry is 4294967295 (no, not -1), this
> won't fit in a signed 32 bit number.
> Does this number come from the SGI or from the NFS stuff in the
> Linux kernel?
It comes from the SGI. The NFS client just considers it all a cookie,
and passes it on to glibc. We probably shouldn't do that, as indeed
the cookie is not guaranteed to be 32-bit signed, but it's what we
always did for 2.2.x.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-18 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 15:21 nfs client problem in kernel 2.4.0 Mogens Kjaer
2001-01-16 15:53 ` Trond Myklebust
2001-01-16 16:04 ` Trond Myklebust
2001-01-18 12:32 ` Mogens Kjaer
2001-01-18 16:10 ` Trond Myklebust [this message]
2001-01-18 16:52 ` Mogens Kjaer
2001-01-17 6:53 ` Mogens Kjaer
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=shsg0igvo19.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mk@crc.dk \
/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