public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>, Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
	Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
	Mike Snitzer <snitzer@kernel.org>
Subject: [PATCH 0/6 RFC] nfsd: provide simpler interface for LOCALIO access
Date: Mon,  1 Jul 2024 12:53:15 +1000	[thread overview]
Message-ID: <20240701025802.22985-1-neilb@suse.de> (raw)

The purpose of this series is to provide an iterface to the filecache
which can be used without a struct svc_rqst, and without any xprt.

This interface is realised in the final patch as nfsd_file_acquire_local().

That function currently takes and nfs_vers option.  That was a natural
fallout of the refactorisation that lead here, but it probably isn't
wanted.  I need to review exactly what effect it has - mostly it is
about error code choice I think.

The function also takess a 'struct auth_domain*'.  It is not clear how a
caller would get hold of such a thing.  I suspect that the server should
register a "local-io" auth_domain in the nfsd_net, and it should be used
here.

Comments on design and implementation most welcome.

Thanks,
NeilBrown

 [PATCH 1/6] nfsd: introduce __fh_verify which takes explicit nfsd_net
 [PATCH 2/6] nfsd: add cred parameter to __fh_verify()
 [PATCH 3/6] nfsd: pass nfs_vers explicitly to __fh_verify()
 [PATCH 4/6] nfsd: pass client explicitly to __fh_verify()
 [PATCH 5/6] nfsd: __fh_verify now treats NULL rqstp as a trusted
 [PATCH 6/6] nfsd: add nfsd_file_acquire_local().

             reply	other threads:[~2024-07-01  2:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  2:53 NeilBrown [this message]
2024-07-01  2:53 ` [PATCH 1/6] nfsd: introduce __fh_verify which takes explicit nfsd_net arg NeilBrown
2024-07-01 14:54   ` Chuck Lever
2024-07-01 15:46   ` kernel test robot
2024-07-01  2:53 ` [PATCH 2/6] nfsd: add cred parameter to __fh_verify() NeilBrown
2024-07-01 11:02   ` Jeff Layton
2024-07-01 17:34   ` kernel test robot
2024-07-01  2:53 ` [PATCH 3/6] nfsd: pass nfs_vers explicitly " NeilBrown
2024-07-01 14:57   ` Chuck Lever
2024-07-01 19:16   ` kernel test robot
2024-07-01  2:53 ` [PATCH 4/6] nfsd: pass client " NeilBrown
2024-07-01 11:12   ` Jeff Layton
2024-07-01  2:53 ` [PATCH 5/6] nfsd: __fh_verify now treats NULL rqstp as a trusted connection NeilBrown
2024-07-01  2:53 ` [PATCH 6/6] nfsd: add nfsd_file_acquire_local() NeilBrown
2024-07-01 11:21   ` Jeff Layton
2024-07-01 23:55     ` NeilBrown
2024-07-02  0:29       ` Jeff Layton
2024-07-04  8:58   ` kernel test robot

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=20240701025802.22985-1-neilb@suse.de \
    --to=neilb@suse.de \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=kolga@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=snitzer@kernel.org \
    --cc=tom@talpey.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox