From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: akpm@digeo.com, tytso@mit.edu
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] htree nfs fix
Date: Wed, 14 May 2003 02:23:57 +0200 [thread overview]
Message-ID: <16065.35997.348432.385925@charged.uio.no> (raw)
Get the facts right please: That rant was bullshit.
NFS tries as hard as it can to interpret the cookie as a bag of
bits. It gets screwed in this by a VFS interface which treats the
32-bit getdents() as having unsigned 32-bit cookies, and the 64-bit
getdents64() as having signed 64-bit cookies.
To make matters worse, glibc comes along and assumes it can use
getdents64 as a substitute for getdents() without having to give any
thought to the problem of cookies.
If you're unhappy with the state of readdir, then fix the VFS/glibc.
At the moment it is simply not possible to write a consistent readdir
at the NFS level.
Trond
next reply other threads:[~2003-05-14 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 0:23 Trond Myklebust [this message]
2003-05-14 0:44 ` Andrew Morton
2003-05-14 9:05 ` Trond Myklebust
2003-05-14 9:12 ` Andrew Morton
2003-05-14 9:32 ` Trond Myklebust
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=16065.35997.348432.385925@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®