From: Chip Salzenberg <chip@pobox.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: "Neil F. Brown" <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Kernel 2.4 and 2.6 disagree about NFSEXP_CROSSMNT - upward incompatibility, please fix
Date: Thu, 31 Jul 2003 11:23:32 -0700 [thread overview]
Message-ID: <20030731182332.GH18733@perlsupport.com> (raw)
In-Reply-To: <3F294DE3.9020304@RedHat.com>
According to Steve Dickson:
> It seems in nfs-utils-1.05 (actually it happen in 1.0.4)
> the NFSEXP_CROSSMNT define was changed to 0x4000 ....
This looks like an actual kernel incompatibility 2.4 <-> 2.6, as
the 2.4 and 2.6 trees disagree about the value of NFSEXP_CROSSMNT.
> So could please add this patch that simply switchs the bits
> so NFSEXP_CROSSMNT stays the same and the new NFSEXP_NOHIDE define
> gets the higher bit?
And 2.6's include/linux/nfsd/export.h needs the same fix. This needs
to go in before the 2.6.0 release or nfs-utils is in deep kimchi.
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
next prev parent reply other threads:[~2003-07-31 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 17:12 nfs-utils-1.0.5 is not backwards compatible with 2.4 Steve Dickson
2003-07-31 18:23 ` Chip Salzenberg [this message]
2003-07-31 22:05 ` Kernel 2.4 and 2.6 disagree about NFSEXP_CROSSMNT - upward incompatibility, please fix Andrew Morton
2003-08-01 2:55 ` nfs-utils-1.0.5 is not backwards compatible with 2.4 Neil Brown
2003-08-01 12:43 ` Steve Dickson
2003-08-04 0:52 ` Neil Brown
2003-08-04 0:52 ` Neil Brown
2003-08-01 14:38 ` Chip Salzenberg
2003-08-04 0:55 ` Neil Brown
2003-08-04 0:55 ` Neil Brown
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=20030731182332.GH18733@perlsupport.com \
--to=chip@pobox.com \
--cc=SteveD@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.