From: David Howells <dhowells@redhat.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: dhowells@redhat.com, Jiri Kosina <trivial@kernel.org>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [TRIVIAL] Documentation: Fix typo 'CONFIG_AFS'
Date: Wed, 25 Jun 2014 10:09:15 +0100 [thread overview]
Message-ID: <6075.1403687355@warthog.procyon.org.uk> (raw)
In-Reply-To: <1403683888.1960.35.camel@x220>
Paul Bolle <pebolle@tiscali.nl> wrote:
> Perhaps AF_RXRPC should be dropped from this short list (it is selected
> if AFS_FS is set). But since I couldn't actually determine how AFS_FS
> and RXKAD interact I decided to not touch that list any further.
The key_type_rxrpc key that the AFS fs or userspace passes to AF_RXRPC
indicates the protocol that AF_RXRPC should use. The AFS fs doesn't need to
care how the security actually works and the token is opaque to it.
rxkad registers itself with AF_RXRPC, which maintains a list. The
security_index is the number that appears in the protocol that indicates the
security driver to use.
David
next prev parent reply other threads:[~2014-06-25 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 8:11 [PATCH] [TRIVIAL] Documentation: Fix typo 'CONFIG_AFS' Paul Bolle
2014-06-25 9:09 ` David Howells [this message]
2014-06-25 9:40 ` Paul Bolle
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=6075.1403687355@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=trivial@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