All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@citi.umich.edu>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Olga Kornievskaia <aglo@citi.umich.edu>, linux-nfs@vger.kernel.org
Subject: new client-side gssd upcall patches
Date: Fri, 12 Dec 2008 13:20:20 -0500	[thread overview]
Message-ID: <1229106035-16102-1-git-send-email-bfields@citi.umich.edu> (raw)


These patches implement the new client-side text-based gssd upcall,
needed for v4.0 callbacks over krb5, better crypto algorithm support,
etc.

All of this is also available from the for-trond branch at

	git://linux-nfs.org/~bfields/linux.git for-trond

Changes since posted versions (mainly the result of testing from Olga):

	- Fix race in pipe creation ordering: gssd uses existance of the
	  two files ("gssd", the new pipe, and "krb5", the old one), to
	  decide what the kernel supports.  If we create "krb5" first,
	  then there's a moment when gssd could think the kernel only
	  supports the old pipe.  So create "gssd" first.
	- Use different pipe operation structures to distinguish the two
	  pipes, instead of depending on comparing to the two dentries
	  in the auth; much simpler code, and avoids a race on open of a
	  new pipe.
	- Reorder initialization in gss_alloc_msg to fix a trivial null
	  dereference in new upcall case.

Comments?  If they look OK to you, please apply at least the first 9.

I've also appended 6 patches that use the new upcall to support krb5
callbacks.  Note a couple of those touch only nfsd.  I was imagining
we'd keep those all together and submit them through your tree.  If you
don't want to do that, could you just ACK the last 6 patches if they're
OK?  And then I'll figure out what to do with them after the rest goes
in.

--b.

             reply	other threads:[~2008-12-12 18:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 18:20 J. Bruce Fields [this message]
2008-12-12 18:20 ` [PATCH 01/15] rpc: remove unnecessary assignment J. Bruce Fields
2008-12-12 18:20   ` [PATCH 02/15] rpc: factor out warning code from gss_pipe_destroy_msg J. Bruce Fields
2008-12-12 18:20     ` [PATCH 03/15] rpc: minor gss_alloc_msg cleanup J. Bruce Fields
2008-12-12 18:20       ` [PATCH 04/15] rpc: add an rpc_pipe_open method J. Bruce Fields
2008-12-12 18:20         ` [PATCH 05/15] rpc: call release_pipe only on last close J. Bruce Fields
2008-12-12 18:20           ` [PATCH 06/15] rpc: track number of users of the gss upcall pipe J. Bruce Fields
2008-12-12 18:20             ` [PATCH 07/15] rpc: use count of pipe openers to wait for first open J. Bruce Fields
2008-12-12 18:20               ` [PATCH 08/15] rpc: store pointer to pipe inode in gss upcall message J. Bruce Fields
2008-12-12 18:20                 ` [PATCH 09/15] rpc: implement new upcall J. Bruce Fields
2008-12-12 18:20                   ` [PATCH 10/15] nfsd: pass client principal name in rsc downcall J. Bruce Fields
2008-12-12 18:20                     ` [PATCH 11/15] rpc: pass target name down to rpc level on callbacks J. Bruce Fields
2008-12-12 18:20                       ` [PATCH 12/15] rpc: allow gss callbacks to client J. Bruce Fields
2008-12-12 18:20                         ` [PATCH 13/15] nfsd: support callbacks with gss flavors J. Bruce Fields
2008-12-12 18:20                           ` [PATCH 14/15] rpc: add target field to new upcall J. Bruce Fields
2008-12-12 18:20                             ` [PATCH 15/15] rpc: add service " 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=1229106035-16102-1-git-send-email-bfields@citi.umich.edu \
    --to=bfields@citi.umich.edu \
    --cc=Trond.Myklebust@netapp.com \
    --cc=aglo@citi.umich.edu \
    --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.