From: Peter Wainwright <prw@ceiriog1.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Irix NFS servers, again :-)
Date: Wed, 16 Jun 2004 19:52:06 +0100 [thread overview]
Message-ID: <1087411925.30092.35.camel@ceiriog1.demon.co.uk> (raw)
I just upgraded one of my machines to Fedora Core 2, including
kernel 2.6.5. I found myself bitten on the bum by a bug I thought
had expired long ago, namely the Irix server readdir bug, or
32/64-bit cookie problem.
Therefore, I thought I should let you folks know that this problem
is still there, apparently.
I searched the LKML archives for (irix OR sgi) and nfs: the most
recent relevant postings seem to be 2 years ago
http://www.uwsg.iu.edu/hypermail/linux/kernel/0204.1/0707.html
http://www.uwsg.iu.edu/hypermail/linux/kernel/0204.2/0163.html
It seems the relevant patch
http://www.fys.uio.no/~trondmy/src/2.4.18/linux-2.4.18-seekdir.dif
was never incorporated in the mainstream kernel; however, Red Hat
did incorporate a similar patch (called, I believe,
linux-2.4.18-irixnfs.patch) in the later 2.4 kernel RPMS. However,
it seems that this has been omitted from the 2.6 kernels in Fedora.
So, I have the old problem: in a directory listing from an NFS
directory mounted from an Irix server, some entries may be
missing.
So, my question is: what happened to this patch? Is there a
2.6 version available somewhere on the net? Was it not
incorporated into the mainstream kernel because it is not the
"right thing" to do (and maybe there is no "right thing" until
we are all running on 64 bits)? If this is the opinion of
the kernel developers I shall chase Red Hat to see if they can
resurrect it when 2.6 kernels appear in their RHEL product.
Some of us unfortunately still need to interoperate with Irix
and other strange systems :-)
If the list is interested, I have "sort of" ported the patch
to Linux 2.6.6 myself - just before I left work this afternoon;
It seems functional, but I need to have another look on my network
at work (where I have the SGI system) before I post it; there may be
other bits that need patching, though I hope my minimal patch will
suffice.
Please CC: to me, as I am not subscribed to the list yet.
next reply other threads:[~2004-06-16 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 18:52 Peter Wainwright [this message]
2004-06-17 9:26 ` David Rees
2004-06-17 13:38 ` Nathan Straz
2004-06-17 17:44 ` Peter Wainwright
2004-06-17 13:44 ` Christoph Hellwig
2004-06-17 16:55 ` Peter Wainwright
2004-06-17 17:54 ` Steve Lord
2004-06-17 18:12 ` Peter Wainwright
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=1087411925.30092.35.camel@ceiriog1.demon.co.uk \
--to=prw@ceiriog1.demon.co.uk \
--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
all inboxes | Powered by JetHome®