All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 00/31] NFS XDR clean up for 2.6.38
Date: Thu, 16 Dec 2010 15:43:43 -0500	[thread overview]
Message-ID: <4D0A79FF.3030800@RedHat.com> (raw)
In-Reply-To: <CD110562-AF52-4A2F-BF74-D7ABC4D58D24@oracle.com>

Hey Chuck,

On 12/16/2010 03:04 PM, Chuck Lever wrote:
> 
> On Dec 16, 2010, at 2:14 PM, Steve Dickson wrote:
> 
>> Hello,
>>
>> I was wondering if it would be possible hold off on committing major 
>> cleans ups like this one (and the RFC: Split nlm_host cache series) 
>> until pNFS wave3 is committed into either Trond's tree and/or in the
>> mainline kernel. 
>>
>> I realize this is a huge request to make, something we've never done
>> before. But talking with the powers to be on this end, include Ric 
>> Wheeler, accepting these types of patches before the pNFS bits 
>> settle down will make close to impossible for there to be any 
>> meaningful pNFS support in the RHEL 6 kernels. We would have 
>> to push the support off to RHEL 7.
>>
>> The reasoning is this, which I do agree with, these types of 
>> patches, although probably needed, do not added any new features 
>> or fix any outstanding bugs.
> 
> The XDR series does add a new feature, FWIW: it adds buffer overflow
> protection to the client's reply processing logic.  Says so right in the 
> patch descriptions.
No... I didn't miss the "bonus" :-) Its just that these are major changes 
in the  bowels of the NFS code at at time  when other major changes (like pNFS) 
are happening... Its just a lot of change happening at once... 

> 
>> More likely than not (for a time) they will 
>> add some instability due to the lack of usage and testing.  These type of 
>> changes are much too large for even our QE group to test and verify and
>> obviously instability is the last thing we can interject into an 
>> on going enterprise product stream.
> 
> The only NFSv4-related changes in this series are limited to refactoring.  
> No behavior changes are made in the NFSv4 code.  The bulk of the changes 
> effect only NFSv2 and NFSv3, and will have no impact on pNFS (other than 
> a minor API change).
We obviously maintaining stability in those version are important too.. ;-) 
Again its just the amount of change and what is changing... 
    
> 
> XDR is straightforward and well understood.  If anything is broken by these 
> patches, I expect it will be exposed quickly.
> 
> The NLM patches also have nothing to do with pNFS, AFAICT, and can likely 
> be skipped for RHEL 6.
I have found pulling major pieces out of major release tends to have
disastrous results... Its an all or nothing thing... 
 
> 
>> Again, I realize what we are asking and how big this request
>> really is. Its just that we've come so far and are pretty close 
>> (IMHO) to have some meaningful  pNFS support in RHEL 6, I 
>> figured I'd take a shoot and ask... 
> 
> I don't think these are as world-bending as you believe.  I'm happy to 
> discuss the actual changes with Ric.
Fantastic!

steved.

  parent reply	other threads:[~2010-12-16 20:43 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 14:54 [PATCH 00/31] NFS XDR clean up for 2.6.38 Chuck Lever
2010-12-14 14:54 ` [PATCH 01/31] NFS: Introduce new-style XDR encoding functions for NFSv2 Chuck Lever
2010-12-14 14:54 ` [PATCH 02/31] NFS: Remove old NFSv2 encoder functions Chuck Lever
2010-12-14 14:54 ` [PATCH 03/31] NFS: Update xdr_encode_foo() functions that we're keeping Chuck Lever
2010-12-14 14:55 ` [PATCH 04/31] NFS: Use the "nfs_stat" enum for nfs_stat_to_errno()'s argument Chuck Lever
2010-12-14 14:55 ` [PATCH 05/31] NFS: Introduce new-style XDR decoding functions for NFSv2 Chuck Lever
2010-12-15 21:48   ` Trond Myklebust
2010-12-15 21:53     ` Trond Myklebust
2010-12-14 14:55 ` [PATCH 06/31] NFS: Replace old NFSv2 decoder functions with xdr_stream-based ones Chuck Lever
2010-12-14 14:55 ` [PATCH 07/31] NFS: Move and update xdr_decode_foo() functions that we're keeping Chuck Lever
2010-12-14 14:55 ` [PATCH 08/31] lockd: Introduce new-style XDR functions for NLMv3 Chuck Lever
2010-12-14 14:55 ` [PATCH 09/31] NFS: Introduce new-style XDR encoding functions for NFSv3 Chuck Lever
2010-12-14 14:56 ` [PATCH 10/31] NFS: Replace old NFSv3 encoder functions with xdr_stream-based ones Chuck Lever
2010-12-14 14:56 ` [PATCH 11/31] NFS: Remove unused old NFSv3 encoder functions Chuck Lever
2010-12-14 14:56 ` [PATCH 12/31] NFS: Update xdr_encode_foo() functions that we're keeping Chuck Lever
2010-12-14 14:56 ` [PATCH 13/31] NFS: Introduce new-style XDR decoding functions for NFSv2 Chuck Lever
2010-12-15 21:49   ` Trond Myklebust
2010-12-16  2:44     ` Chuck Lever
2010-12-14 14:56 ` [PATCH 14/31] NFS: Switch in new NFSv3 decoder functions Chuck Lever
2010-12-14 14:56 ` [PATCH 15/31] NFS: Remove unused old " Chuck Lever
2010-12-14 14:57 ` [PATCH 16/31] NFS: Move and update xdr_decode_foo() functions that we're keeping Chuck Lever
2010-12-14 14:57 ` [PATCH 17/31] lockd: Introduce new-style XDR functions for NLMv4 Chuck Lever
2010-12-14 14:57 ` [PATCH 18/31] NFSD: Update XDR encoders in NFSv4 callback client Chuck Lever
2010-12-14 14:57 ` [PATCH 19/31] NFSD: Update XDR decoders " Chuck Lever
2010-12-14 14:57 ` [PATCH 20/31] NFS: Repair whitespace damage in NFS PROC macro Chuck Lever
2010-12-14 14:57 ` [PATCH 21/31] lockd: Move nlmdbg_cookie2a() to svclock.c Chuck Lever
2010-12-14 14:58 ` [PATCH 22/31] NFS: Fix hdrlen calculation in NFSv4's decode_read() Chuck Lever
2010-12-14 14:58 ` [PATCH 23/31] NFS: Simplify ->decode_dirent() calling sequence Chuck Lever
2010-12-14 14:58 ` [PATCH 24/31] NFS: Squelch compiler warning in decode_getdeviceinfo() Chuck Lever
2010-12-14 14:58 ` [PATCH 25/31] NSM: Avoid return code checking in NSM XDR encoder functions Chuck Lever
2010-12-14 14:58 ` [PATCH 26/31] NFS: Avoid return code checking in mount " Chuck Lever
2010-12-14 14:58 ` [PATCH 27/31] NFS: Remove unused UMNT response data structure Chuck Lever
2010-12-14 14:58 ` [PATCH 28/31] SUNRPC: Avoid return code checking in rpcbind XDR encoder functions Chuck Lever
2010-12-14 14:59 ` [PATCH 29/31] SUNRPC: Determine value of "nrprocs" automatically Chuck Lever
2010-12-14 14:59 ` [PATCH 30/31] SUNRPC: New xdr_streams XDR encoder API Chuck Lever
2010-12-14 14:59 ` [PATCH 31/31] SUNRPC: New xdr_streams XDR decoder API Chuck Lever
2010-12-16 19:14 ` [PATCH 00/31] NFS XDR clean up for 2.6.38 Steve Dickson
2010-12-16 20:04   ` Chuck Lever
2010-12-16 20:21     ` Ric Wheeler
2010-12-16 21:04       ` Chuck Lever
2010-12-16 22:45         ` Ric Wheeler
2010-12-16 20:43     ` Steve Dickson [this message]
2010-12-16 23:05   ` Christoph Hellwig
2010-12-16 23:14     ` Ric Wheeler
2010-12-16 23:16       ` Christoph Hellwig
2010-12-16 23:24         ` Ric Wheeler
2010-12-16 23:30     ` Ric Wheeler
2010-12-16 23:40       ` Christoph Hellwig
2010-12-17  3:32         ` Trond Myklebust
2010-12-17 14:56           ` Steve Dickson
2010-12-17 17:11           ` Chuck Lever
2010-12-17 22:44             ` Ric Wheeler
2010-12-17 12:16     ` Steve Dickson

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=4D0A79FF.3030800@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.com \
    /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.