From: Andrew Morton <akpm@linux-foundation.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: staubach@redhat.com, nfsv4@linux-nfs.org,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
trond.myklebust@fys.uio.no
Subject: Re: What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Thu, 4 Oct 2007 11:42:43 -0700 [thread overview]
Message-ID: <20071004114243.3161af16.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071004184304.6e71ab6d@poseidon.drzeus.cx>
On Thu, 4 Oct 2007 18:43:04 +0200
Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> On Thu, 04 Oct 2007 10:00:50 -0400
> Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> > On Thu, 2007-10-04 at 08:52 +0200, Pierre Ossman wrote:
> > > On Wed, 03 Oct 2007 19:41:16 -0400
> > > Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> > >
> > > >
> > > > We also have the 64-bit inode support from RedHat/Peter Staubach.
> > > >
> > >
> > > As has been pointed[1] out[2], this will cause regressions for
> > > non-LFS applications (of which there are still lots and lots). This
> > > change should be in feature-removal (the "feature" being removed is
> > > legacy support for non-LFS applications using NFS servers that make
> > > full use of the protocol) and preferably accompanied with
> > > appropriate user space changes (e.g. compatibility option in glibc).
> > >
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=241348
> > > [2] http://marc.info/?l=linux-nfs&m=118701088726477&w=2
> > >
> > > Rgds
> >
> > How about a boot/module parameter to turn it on or off?
> >
>
> That would be perfect. It can even be in non-legacy mode by default,
> just as long as you can go back to the old behaviour when/if you run
> into a non-LFS application.
>
Wouldn't a mount option be better?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: trond.myklebust@fys.uio.no, staubach@redhat.com,
nfsv4@linux-nfs.org, nfs@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [NFS] What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree...
Date: Thu, 4 Oct 2007 11:42:43 -0700 [thread overview]
Message-ID: <20071004114243.3161af16.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071004184304.6e71ab6d@poseidon.drzeus.cx>
On Thu, 4 Oct 2007 18:43:04 +0200
Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> On Thu, 04 Oct 2007 10:00:50 -0400
> Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> > On Thu, 2007-10-04 at 08:52 +0200, Pierre Ossman wrote:
> > > On Wed, 03 Oct 2007 19:41:16 -0400
> > > Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> > >
> > > >
> > > > We also have the 64-bit inode support from RedHat/Peter Staubach.
> > > >
> > >
> > > As has been pointed[1] out[2], this will cause regressions for
> > > non-LFS applications (of which there are still lots and lots). This
> > > change should be in feature-removal (the "feature" being removed is
> > > legacy support for non-LFS applications using NFS servers that make
> > > full use of the protocol) and preferably accompanied with
> > > appropriate user space changes (e.g. compatibility option in glibc).
> > >
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=241348
> > > [2] http://marc.info/?l=linux-nfs&m=118701088726477&w=2
> > >
> > > Rgds
> >
> > How about a boot/module parameter to turn it on or off?
> >
>
> That would be perfect. It can even be in non-legacy mode by default,
> just as long as you can go back to the old behaviour when/if you run
> into a non-LFS application.
>
Wouldn't a mount option be better?
next prev parent reply other threads:[~2007-10-04 18:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 23:41 What's slated for inclusion in 2.6.24-rc1 from the NFS client git tree Trond Myklebust
2007-10-03 23:41 ` Trond Myklebust
2007-10-03 23:52 ` Jeff Garzik
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 6:52 ` Pierre Ossman
2007-10-04 14:00 ` [NFS] " Trond Myklebust
2007-10-04 14:00 ` Trond Myklebust
2007-10-04 16:43 ` Pierre Ossman
2007-10-04 18:42 ` Andrew Morton [this message]
2007-10-04 18:42 ` Andrew Morton
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:16 ` Trond Myklebust
2007-10-04 19:41 ` Peter Staubach
2007-10-04 19:41 ` [NFS] " Peter Staubach
2007-10-05 6:25 ` Pierre Ossman
2007-10-05 6:25 ` [NFS] " Pierre Ossman
2007-10-05 12:24 ` Jeff Layton
2007-10-05 17:36 ` [NFS] " Trond Myklebust
2007-10-05 17:54 ` Pierre Ossman
2007-10-05 17:54 ` [NFS] " Pierre Ossman
2007-10-04 19:59 ` Andrew Morton
2007-10-04 19:59 ` Andrew Morton
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 0:58 ` Trond Myklebust
2007-10-05 17:30 ` Valdis.Kletnieks
2007-10-05 17:30 ` [NFS] " Valdis.Kletnieks
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 17:52 ` Trond Myklebust
2007-10-05 18:00 ` Jeff Layton
2007-10-05 18:00 ` [NFS] " Jeff Layton
2007-10-08 8:36 ` Greg Banks
2007-10-05 18:12 ` Jeff Layton
2007-10-05 18:12 ` Jeff Layton
2007-10-07 22:56 ` David Chinner
2007-10-04 20:16 ` Chuck Lever
2007-10-05 17:31 ` 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=20071004114243.3161af16.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=staubach@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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.