From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: stateid handling improvements
Date: Thu, 18 Jun 2015 17:19:16 -0400 [thread overview]
Message-ID: <20150618211916.GA21903@fieldses.org> (raw)
In-Reply-To: <1434638702-353-1-git-send-email-hch@lst.de>
On Thu, Jun 18, 2015 at 04:44:57PM +0200, Christoph Hellwig wrote:
> Ensure that we allocate a file structure in nfs4_preprocess_stateid_op
> for all callers that as for it to consolidate code and fix the handling
> of ALLOCATE, DEALLOCATE and SEEK to match the latest NFSv4.2 drafts.
Those make sense to me, thanks.
Applying pending some testing.
--b.
prev parent reply other threads:[~2015-06-18 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 14:44 stateid handling improvements Christoph Hellwig
2015-06-18 14:44 ` [PATCH 1/5] nfsd: clean up raparams handling Christoph Hellwig
2015-06-18 14:44 ` [PATCH 2/5] nfsd: refactor nfs4_preprocess_stateid_op Christoph Hellwig
2015-06-18 14:45 ` [PATCH 3/5] nfsd: take struct file setup fully into nfs4_preprocess_stateid_op Christoph Hellwig
2015-06-18 14:45 ` [PATCH 4/5] nfsd: fput rd_file from XDR encode context Christoph Hellwig
2015-06-18 14:45 ` [PATCH 5/5] nfsd: wrap too long lines in nfsd4_encode_read Christoph Hellwig
2015-06-18 21:19 ` J. Bruce Fields [this message]
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=20150618211916.GA21903@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@lst.de \
--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 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.