All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Boeckel <mathstuf@gmail.com>
To: keyrings@vger.kernel.org
Subject: [PATCH 3/5] rxrpc: mention that client key payloads are not arbitrary
Date: Thu, 27 Sep 2018 13:14:48 +0000	[thread overview]
Message-ID: <20180927131450.23458-4-mathstuf@gmail.com> (raw)

Signed-off-by: Ben Boeckel <mathstuf@gmail.com>
---
 net/rxrpc/key.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/rxrpc/key.c b/net/rxrpc/key.c
index e7f6b8823eb6..51fb50541397 100644
--- a/net/rxrpc/key.c
+++ b/net/rxrpc/key.c
@@ -38,8 +38,8 @@ static void rxrpc_describe(const struct key *, struct seq_file *);
 static long rxrpc_read(const struct key *, char __user *, size_t);
 
 /*
- * rxrpc defined keys take an arbitrary string as the description and an
- * arbitrary blob of data as the payload
+ * rxrpc defined keys take an arbitrary string as the description. See
+ * rxrpc_preparse for the payload format.
  */
 struct key_type key_type_rxrpc = {
 	.name		= "rxrpc",
-- 
2.17.1

             reply	other threads:[~2018-09-27 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 13:14 Ben Boeckel [this message]
2018-09-27 17:12 ` [PATCH 3/5] rxrpc: mention that client key payloads are not arbitrary David Howells

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=20180927131450.23458-4-mathstuf@gmail.com \
    --to=mathstuf@gmail.com \
    --cc=keyrings@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.