public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Anna Schumaker <anna.schumaker@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] NFSD: Add v4.2 SEEK support
Date: Wed, 1 Oct 2014 14:21:07 -0400	[thread overview]
Message-ID: <20141001182106.GB29675@fieldses.org> (raw)
In-Reply-To: <CAFX2Jfm2pDmz7vKPVNe8yZScVT-MvVD=+AsfOgdrPfKwgaLTXw@mail.gmail.com>

On Tue, Sep 30, 2014 at 01:00:24PM -0400, Anna Schumaker wrote:
> I'm testing with xfstests #285.  It's an lseek specific test, and helped
> find a few edge cases during development.

I think you told me that already and I forgot.  Bah.

OK, applied.  Thanks!

--b.

> 
> Anna
> 
> On Fri, Sep 26, 2014 at 5:54 PM, J. Bruce Fields <bfields@fieldses.org>
> wrote:
> 
> > On Fri, Sep 26, 2014 at 01:58:25PM -0400, Anna.Schumaker@netapp.com wrote:
> > > From: Anna Schumaker <Anna.Schumaker@Netapp.com>
> > >
> > > These patches add server support for the NFS v4.2 operation SEEK.  The
> > first
> > > patch adds basic NFS v4.2 infrastructure that all future operations will
> > rely
> > > on.  The second patch adds the SEEK operation.
> >
> > How are you testing these?
> >
> > It looks OK to me, so I'll likely commit in a few days if there are no
> > objections.
> >
> > --b.
> >
> > >
> > > Changes in v3:
> > > - Rework the switch statement in nfsd4_seek() so we only call
> > vfs_llseek()
> > >   from one place.
> > > - Change XDR encode and decode functions to A + B notation for
> > calculating
> > >   byte counts.
> > >
> > > These patches and the corresponding client patch are avaliable in the
> > [seek]
> > > branch of:
> > >
> > >       git://git.linux-nfs.org/projects/anna/linux-nfs.git
> > >
> > >
> > > Questions?  Comments?  Thoughts?
> > >
> > > Anna
> > >
> > >
> > > Anna Schumaker (2):
> > >   NFSD: Add generic v4.2 infrastructure
> > >   NFSD: Implement SEEK
> > >
> > >  fs/nfsd/nfs4proc.c   | 49 ++++++++++++++++++++++++++++++++++++++++++
> > >  fs/nfsd/nfs4xdr.c    | 60
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >  fs/nfsd/xdr4.h       | 14 ++++++++++++
> > >  include/linux/nfs4.h | 23 ++++++++++++++++++--
> > >  4 files changed, 144 insertions(+), 2 deletions(-)
> > >
> > > --
> > > 2.1.0
> > >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >

  parent reply	other threads:[~2014-10-01 18:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 17:58 [PATCH v3 0/2] NFSD: Add v4.2 SEEK support Anna.Schumaker
2014-09-26 17:58 ` [PATCH v3 1/2] NFSD: Add generic v4.2 infrastructure Anna.Schumaker
2014-09-26 17:58 ` [PATCH v3 2/2] NFSD: Implement SEEK Anna.Schumaker
2014-09-26 21:54 ` [PATCH v3 0/2] NFSD: Add v4.2 SEEK support J. Bruce Fields
     [not found]   ` <CAFX2Jfm2pDmz7vKPVNe8yZScVT-MvVD=+AsfOgdrPfKwgaLTXw@mail.gmail.com>
2014-10-01 18:21     ` J. Bruce Fields [this message]
2014-10-28 21:07     ` J. Bruce Fields
2014-10-28 21:09       ` Anna Schumaker
2014-10-28 21:17         ` J. Bruce Fields
2014-10-28 21:24           ` J. Bruce Fields
2014-10-28 21:29             ` Anna Schumaker
2014-10-28 21:30             ` J. Bruce Fields

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=20141001182106.GB29675@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox