From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "H . J . Lu" <hjl@valinux.com>
Cc: NFS maillist <nfs@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] Updated patch for the [2.4.x] NFS 'missing directory entry a.k.a. IRIX server' problem...
Date: Tue, 27 Feb 2001 08:41:15 +0100 (CET) [thread overview]
Message-ID: <15003.23067.683600.738764@charged.uio.no> (raw)
In-Reply-To: <20010226230647.A14094@valinux.com>
In-Reply-To: <14997.9938.106305.635202@charged.uio.no> <20010226152826.A20653@valinux.com> <15003.20448.999929.948597@charged.uio.no> <20010226230647.A14094@valinux.com>
>>>>> " " == H J Lu <hjl@valinux.com> writes:
> I much prefer to have a new getdents system call which will
> also return d_type so that the 32 bit function in glibc can use
> this new getdents instead of getdents64.
That could also be done, however it seems odd to be adding a new
32-bit interface after the point when we're supposed to all have moved
to 64 bits.
My concern in presenting that patch is simply that if it is true that
we actually have a well defined interface for passing 32-bit cookies
via getdents64, and if it is true that everybody agrees on this
interface, then NFS has no choice but to try to conform.
Cheers,
Trond
BTW: does anybody anywhere actually use d_type? Certainly the standard
utilities such as 'find' or 'ls' don't seem to have been adapted
yet: I hacked up a version of NFSv3 that actually filled d_type
(by using readdirplus rather than readdir) but I've yet to find
any 'off the shelf' software, that uses the extra information.
next prev parent reply other threads:[~2001-02-27 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 14:48 Updated patch for the [2.4.x] NFS 'missing directory entry a.k.a. IRIX server' problem Trond Myklebust
2001-02-26 23:28 ` [NFS] " H . J . Lu
2001-02-27 6:57 ` Trond Myklebust
2001-02-27 7:06 ` H . J . Lu
2001-02-27 7:41 ` Trond Myklebust [this message]
2001-02-27 19:12 ` Jamie Lokier
2001-02-27 23:04 ` H . J . Lu
2001-02-27 23:24 ` H . J . Lu
2001-02-28 11:19 ` 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=15003.23067.683600.738764@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=hjl@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).