LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Michael Halcrow <mhalcrow@us.ibm.com> To: Andrew Morton <akpm@linux-foundation.org> Cc: linux-kernel@vger.kernel.org, dustin.kirkland@gmail.com, sandeen@redhat.com, tchicks@us.ibm.com, shaggy@us.ibm.com Subject: [PATCH] eCryptfs: kerneldoc for ecryptfs_parse_tag_70_packet() Date: Wed, 12 Nov 2008 11:06:40 -0600 [thread overview] Message-ID: <20081112170640.GD6842@halcrowt61p.austin.ibm.com> (raw) In-Reply-To: <20081106141234.ba53c112.akpm@linux-foundation.org> On Thu, Nov 06, 2008 at 02:12:34PM -0800, Andrew Morton wrote: > On Tue, 4 Nov 2008 15:39:08 -0600 > Michael Halcrow <mhalcrow@us.ibm.com> wrote: > > +/** > > + * parse_tag_70_packet - Parse and process FNEK-encrypted passphrase packet > > + * @filename: This function kmalloc's the memory for the filename > > + */ > > This kernedoc missed lots of the arguments. Kerneldoc updates for ecryptfs_parse_tag_70_packet(). Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com> --- fs/ecryptfs/keystore.c | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c index 71dcf0e..3c90250 100644 --- a/fs/ecryptfs/keystore.c +++ b/fs/ecryptfs/keystore.c @@ -771,6 +771,17 @@ struct ecryptfs_parse_tag_70_packet_silly_stack { /** * parse_tag_70_packet - Parse and process FNEK-encrypted passphrase packet * @filename: This function kmalloc's the memory for the filename + * @filename_size: This function sets this to the amount of memory + * kmalloc'd for the filename + * @packet_size: This function sets this to the the number of octets + * in the packet parsed + * @mount_crypt_stat: The mount-wide cryptographic context + * @data: The memory location containing the start of the tag 70 + * packet + * @max_packet_size: The maximum legal size of the packet to be parsed + * from @data + * + * Returns zero on success; non-zero otherwise */ int ecryptfs_parse_tag_70_packet(char **filename, size_t *filename_size, -- 1.5.3.7
next prev parent reply other threads:[~2008-11-12 17:06 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-04 21:37 [PATCH 0/5] eCryptfs: Filename Encryption Michael Halcrow 2008-11-04 21:39 ` [PATCH 1/5] eCryptfs: Filename Encryption: Tag 70 packets Michael Halcrow 2008-11-06 22:12 ` Andrew Morton 2008-11-12 17:01 ` [PATCH] eCryptfs: Replace %Z with %z Michael Halcrow 2008-11-12 17:04 ` [PATCH] eCryptfs: Fix data types (int/size_t) Michael Halcrow 2008-11-12 17:06 ` Michael Halcrow [this message] 2008-11-04 21:39 ` [PATCH 2/5] eCryptfs: Filename Encryption: Header updates Michael Halcrow 2008-11-04 21:41 ` [PATCH 3/5] eCryptfs: Filename Encryption: Encoding and encryption functions Michael Halcrow 2008-11-05 18:17 ` Dave Hansen 2008-11-06 21:01 ` Michael Halcrow 2008-11-06 22:12 ` Andrew Morton 2008-11-12 17:11 ` [PATCH] eCryptfs: Clean up ecryptfs_decode_from_filename() Michael Halcrow 2008-11-04 21:42 ` [PATCH 4/5] eCryptfs: Filename Encryption: filldir, lookup, and readlink Michael Halcrow 2008-11-04 21:43 ` [PATCH 5/5] eCryptfs: Filename Encryption: mount option Michael Halcrow 2008-11-06 22:13 ` Andrew Morton 2008-11-14 16:47 ` Michael Halcrow 2008-11-05 15:57 ` [PATCH 0/5] eCryptfs: Filename Encryption Pavel Machek 2008-11-06 20:27 ` Michael Halcrow 2008-11-06 20:52 ` Dave Kleikamp 2008-11-06 22:11 ` Michael Halcrow
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=20081112170640.GD6842@halcrowt61p.austin.ibm.com \ --to=mhalcrow@us.ibm.com \ --cc=akpm@linux-foundation.org \ --cc=dustin.kirkland@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=sandeen@redhat.com \ --cc=shaggy@us.ibm.com \ --cc=tchicks@us.ibm.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: linkBe 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; as well as URLs for NNTP newsgroup(s).