From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Michael Halcrow" <mhalcrow@us.ibm.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, toml@us.ibm.com
Subject: Re: [PATCH 4/7] eCryptfs: Comments for some structs
Date: Thu, 26 Jul 2007 04:29:31 +0530 [thread overview]
Message-ID: <a781481a0707251559n1fc8bb1y343e980deb25377b@mail.gmail.com> (raw)
In-Reply-To: <20070725205135.GU14091@halcrow.austin.ibm.com>
Trivial nits ...
On 7/26/07, Michael Halcrow <mhalcrow@us.ibm.com> wrote:
> [...]
> +/**
> + * ecryptfs_global_auth_tok structs refer to authentication token keys
> + * in the user keyring that apply to newly created files. A list of
> + * these objects hangs off of the mount_crypt_stat struct for any
> + * given eCryptfs mount. This struct maintains a reference to both the
> + * key contents and the key itself so that the key can be put on
> + * unmount.
> + */
/** is used to annotate kernel-doc style comments, which this
one isn't -- IIRC, kernel-doc doesn't like this (?)
> struct ecryptfs_global_auth_tok {
> #define ECRYPTFS_AUTH_TOK_INVALID 0x00000001
> u32 flags;
> - struct list_head mount_crypt_stat_list;
> - struct key *global_auth_tok_key;
> - struct ecryptfs_auth_tok *global_auth_tok;
> - unsigned char sig[ECRYPTFS_SIG_SIZE_HEX + 1];
> + struct list_head mount_crypt_stat_list; /* Default auth_tok list for
> + * the mount_crypt_stat */
> + struct key *global_auth_tok_key; /* The key from the user's keyring for
> + * the sig */
Tsk. You could consider using kernel-doc style itself to comment the
structure -- this stuff goes up there and doesn't look icky.
> + struct ecryptfs_auth_tok *global_auth_tok; /* The key contents */
> + unsigned char sig[ECRYPTFS_SIG_SIZE_HEX + 1]; /* The key identifier */
> };
>
> +/**
> + * Typically, eCryptfs will use the same ciphers repeatedly throughout
> + * the course of its operations. In order to avoid unnecessarily
> + * destroying and initializing the same cipher repeatedly, eCryptfs
> + * keeps a list of crypto API contexts around to use when needed.
> + */
Again, you could consider using kernel-doc style comments here.
> struct ecryptfs_key_tfm {
> struct crypto_blkcipher *key_tfm;
> size_t key_size;
> struct mutex key_tfm_mutex;
> - struct list_head key_tfm_list;
> + struct list_head key_tfm_list; /* The module's tfm list */
> unsigned char cipher_name[ECRYPTFS_MAX_CIPHER_NAME_SIZE + 1];
> };
Satyam
next prev parent reply other threads:[~2007-07-25 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 20:48 [PATCH 0/7] eCryptfs: Trivial updates Michael Halcrow
2007-07-25 20:49 ` [PATCH 1/7] eCryptfs: Remove unnecessary BUG_ON Michael Halcrow
2007-07-25 20:50 ` [PATCH 2/7] eCryptfs: Collapse flag set into one statement Michael Halcrow
2007-07-25 20:50 ` [PATCH 3/7] eCryptfs: Grammatical fix (destruct to destroy) Michael Halcrow
2007-07-25 20:51 ` [PATCH 4/7] eCryptfs: Comments for some structs Michael Halcrow
2007-07-25 22:59 ` Satyam Sharma [this message]
2007-07-25 20:52 ` [PATCH 5/7] eCryptfs: kerneldoc fixes for crypto.c and keystore.c Michael Halcrow
2007-07-25 20:52 ` [PATCH 6/7] eCryptfs: Remove unnecessary variable initializations Michael Halcrow
2007-07-25 20:53 ` [PATCH 7/7] eCryptfs: Make needlessly global symbols static 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=a781481a0707251559n1fc8bb1y343e980deb25377b@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=toml@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: 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
all inboxes | Powered by JetHome®