From: Herbert Xu <herbert@gondor.apana.org.au>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: compress - Add pcomp interface
Date: Thu, 19 Feb 2009 18:42:51 +0800 [thread overview]
Message-ID: <20090219104250.GA9633@gondor.apana.org.au> (raw)
In-Reply-To: <alpine.LRH.2.00.0902191005110.27630@vixen.sonytel.be>
On Thu, Feb 19, 2009 at 10:12:18AM +0100, Geert Uytterhoeven wrote:
>
> IIUC, my setup() routines should decode the parameters using nla_parse()?
Right.
> And the caller of a setup() routine should encode the data. But how? All the
> nla_put*() routines seem to be targeted at skb's.
The callers in the kernel should just lay it out on the stack, e.g.,
struct {
struct nlattr foo;
u32 foo_val;
struct nlattr bar;
u32 bar_val;
...
};
Note that the netlink alignment is 4 so u32 doesn't need any padding
though u8/u16 would need padding before the next nlattr. Although
for our purposes u32 should be sufficient.
> The only place where nla_parse() is called with a void */length pair is
> net/sched/em_meta.c:em_meta_change(). But I can find no place where the actual
> TCA_EM_META_* fields are encoded.
For simple things like u32 the format is just header followed by
the u32. See nla_get_u32 for details.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2009-02-19 10:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 15:59 [PATCH/RFC 0/7] Partial (de)compression API Geert Uytterhoeven
2009-01-13 15:59 ` [PATCH] crypto: compress - Add pcomp interface Geert Uytterhoeven
2009-01-13 15:59 ` [PATCH] crypto: testmgr - Add support for the " Geert Uytterhoeven
2009-01-13 15:59 ` [PATCH] crypto: api - Add type init function to crypto_tfm Geert Uytterhoeven
2009-01-13 15:59 ` [PATCH] crypto: api - Export pcomp through comp Geert Uytterhoeven
2009-01-13 15:59 ` [PATCH] crypto: deflate - switch to pcomp Geert Uytterhoeven
2009-01-13 15:59 ` [PATCH] crypto: testmgr - swith deflate test " Geert Uytterhoeven
2009-01-13 15:59 ` [PATCH] squashfs: Make SquashFS 4 use the new pcomp crypto interface Geert Uytterhoeven
2009-01-14 3:16 ` [PATCH] crypto: compress - Add pcomp interface Herbert Xu
2009-01-14 15:01 ` Geert Uytterhoeven
2009-01-15 3:05 ` Herbert Xu
2009-01-15 10:54 ` Geert Uytterhoeven
2009-01-16 4:27 ` Herbert Xu
2009-02-05 16:24 ` Geert Uytterhoeven
2009-02-10 6:18 ` Herbert Xu
2009-02-12 15:19 ` Geert Uytterhoeven
2009-02-19 4:08 ` Herbert Xu
2009-02-19 9:12 ` Geert Uytterhoeven
2009-02-19 10:42 ` Herbert Xu [this message]
2009-02-23 17:32 ` Geert Uytterhoeven
2009-02-25 2:56 ` Herbert Xu
2009-02-25 13:26 ` Geert Uytterhoeven
2009-01-14 16:45 ` Jaswinder Singh Rajput
2009-01-14 16:54 ` Geert Uytterhoeven
2009-01-14 17:08 ` Jaswinder Singh Rajput
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=20090219104250.GA9633@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 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®