All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: "Peter Åstrand" <astrand@cendio.se>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	NFS List <nfs@lists.sourceforge.net>,
	Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [PATCH] 64 bit ino support for NFS client
Date: Mon, 13 Aug 2007 09:27:28 -0400	[thread overview]
Message-ID: <46C05C40.30707@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708131511470.15451@maggie.lkpg.cendio.se>

Peter =C5strand wrote:
> On Fri, 3 Aug 2007, Peter Staubach wrote:
>
>> Attached is a patch to modify the NFS client code to support
>> 64 bit ino's, as appropriate for the system and the NFS
>> protocol version.
>>
>> The code basically just expand the NFS interfaces for routines
>> which handle ino's from using ino_t to u64 and then uses the
>> fileid in the nfs_inode instead of i_ino in the inode.  The
>
> This patch seems to overlap with =

> linux-2.6-nfs-64-bit-inode-support.patch, which is included in RHEL5 =

> kernels. Are these patches related, somehow? The RHEL5 patch causes =

> problems, as described at =

> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D241348. =


They are related in that they modify similar areas in the NFS code.
However, this patch only modifies the NFS code and not the rest of
the file systems and areas in the kernel.

My opinion on the referenced bugzilla is that things change and
it may be time to update applications and such to work in the
new world.  Applications which do not get modified, tend to work
less and less as time goes by because while the world changes
around them, they don't.

I don't believe that this is the only cause which will keep those
applications from working completely.  With the addition of the
LFS thing, they will start to encounter more and more things that
they are not prepared to deal with.

    Thanx...

       ps

-------------------------------------------------------------------------
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

  reply	other threads:[~2007-08-13 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 19:07 [PATCH] 64 bit ino support for NFS client Peter Staubach
2007-08-11 15:12 ` Trond Myklebust
2007-08-13 13:14 ` Peter Åstrand
2007-08-13 13:27   ` Peter Staubach [this message]
2007-08-13 14:12     ` Peter Åstrand
2007-08-13 14:46       ` Peter Staubach
2007-08-13 16:04         ` Peter Åstrand
2007-08-13 16:12       ` Trond Myklebust
     [not found]         ` <1187022103.6628.12.camel@heimdal.trondhjem.org>
2007-08-13 16:46           ` Peter Åstrand
2007-08-13 16:57             ` Trond Myklebust
2007-08-13 17:54               ` Peter Åstrand
     [not found]                 ` <1187033724.6628.82.camel@heimdal.trondhjem.org>
2007-08-14  7:58                   ` Peter Åstrand
2007-08-14 12:58                     ` Jeff Layton

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=46C05C40.30707@redhat.com \
    --to=staubach@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=astrand@cendio.se \
    --cc=nfs@lists.sourceforge.net \
    --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.