- Subject: Re: [PATCH v1.5 5/5] keys: add new key-type encrypted
- From: David Howells <dhowells@xxxxxxxxxx>
- Date: Wed, 08 Dec 2010 10:54:24 +0000
- Cc: dhowells@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-security-module@xxxxxxxxxxxxxxx, keyrings@xxxxxxxxxxxxx, linux-crypto@xxxxxxxxxxxxxxx, Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx>, James Morris <jmorris@xxxxxxxxx>, David Safford <safford@xxxxxxxxxxxxxx>, Rajiv Andrade <srajiv@xxxxxxxxxxxxxxxxxx>
- In-reply-to: <1291762122.2680.31.camel@xxxxxxxxxxxxxxxxxxxxx>
- Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903
Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx> wrote:
> > > +static struct key *request_trusted_key(const char *trusted_desc,
> > > + u8 **master_key,
> > > + unsigned int *master_keylen)
> >
> > You need to annotate the function with an __acquires() to indicate that it
> > returns with a lock held for Sparse checking. I think you should be able to
> > do:
> >
> > __acquires(tkey->sem)
>
> hm, only after addding '__acquires' are there Sparse errors.
Leave it, then.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Kernel]
[Gnu Classpath]
[Gnu Crypto]
[DM Crypt]
[Netfilter]
[Bugtraq]