From: Bryan Schumaker <bjschuma@netapp.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>
Subject: [PATCH v3 0/5] Add secinfo t othe NFS client
Date: Thu, 06 Jan 2011 16:58:38 -0500 [thread overview]
Message-ID: <4D263B0E.4060905@netapp.com> (raw)
These patches will add the secinfo procedure to the NFS client
and do some cleanup along the way. The final result will should
be able to cross mountpoints using a different form of security
and auto-detect the security of an initial NFS v4 mount.
v3:
- Check for server returning too many security flavors
- Check for gss_oid_len > max_gss_oid_len
- New functions in namespace.c should be static
v2:
- Add more details about the call_sync improvement
- Don't initialize global constant function pointers to NULL
Bryan
reply other threads:[~2011-01-06 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D263B0E.4060905@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@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 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.