[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2E1EB2CF9ED1CB4AA966F0EB76EAB4430A777FE7@SACMVEXC2-PRD.hq.netapp.com>
Date: Sun, 31 Jul 2011 11:30:48 -0700
From: "Myklebust, Trond" <Trond.Myklebust@...app.com>
To: "Christoph Hellwig" <hch@...radead.org>
Cc: "Linus Torvalds" <torvalds@...ux-foundation.org>,
<linux-fsdevel@...r.kernel.org>, <linux-nfs@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: RE: Please pull NFS client changes
> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@...radead.org]
> Sent: Sunday, July 31, 2011 2:24 PM
> To: Myklebust, Trond
> Cc: Linus Torvalds; linux-fsdevel@...r.kernel.org; linux-
> nfs@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: Re: Please pull NFS client changes
>
> How does this manage to include the pnfs block code, which only was
> posted
> on the list a few hours before the pull request, and which doesn't
> appear to past testing very well (although the major issue seems to be
> core nfs code)?
The majority of that code has been ready for several weeks and has been
posted several times for review. The main stuff that was addressed in
the last week were smaller issues such as the naming of functions that
are globally visible (i.e. not polluting the kernel namespace), a few
bisectability issues and (in the last iteraction) the lack of a
signed-off-by: from Jim.
I agree that we have to address the bug that Peng found, but that
appears to be linked to the NFSv4.1 back channel, which these patches
did not change.
The other point to note is that the patches do not touch the main
read/write code and only lightly change the pNFS code paths. The impact
of any residual bugs is therefore going to be limited.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists