From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Shasi Pulijala <spulijala@amcc.com>
Cc: linux-crypto@vger.kernel.org, Loc Ho <lho@amcc.com>
Subject: Re: OpenSSL patch to support Linux CryptoAPI.
Date: Sat, 9 Aug 2008 01:09:49 +0400 [thread overview]
Message-ID: <20080808210949.GA6535@2ka.mipt.ru> (raw)
In-Reply-To: <DB599F406D04E34389140B7D99C71B1B05D9E002@SDCEXCHANGE01.ad.amcc.com>
Hi.
On Fri, Aug 08, 2008 at 11:31:58AM -0700, Shasi Pulijala (spulijala@amcc.com) wrote:
> struct crypt_op {
> - u_int32_t ses;
> - u_int16_t op; /* i.e. COP_ENCRYPT */
> #define COP_NONE 0
> #define COP_ENCRYPT 1
> #define COP_DECRYPT 2
> - u_int16_t flags;
> -#define COP_F_BATCH 0x0008 /* Batch op if possible */
> - u_int len;
> - caddr_t src, dst; /* become iov[] inside kernel */
> - caddr_t mac; /* must be big enough for chosen MAC */
> - caddr_t iv;
> + __u16 op; /* i.e. COP_ENCRYPT */
> + __u16 flags;
> + __u16 iv_size;
> + __u16 assoc_size;
> + __u32 src_size;
> + caddr_t src_data;
> + caddr_t dst_data;
> + __u8 data[0]; /* must be big enough for chosen MAC */
> };
If above caddr_t is what I thought (i.e. a pointer or long type),
there is no way it can be correct. It is _NOT_ allowed to put
variable sized members into structures shared between kernel
and userspace.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-08-08 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 18:31 OpenSSL patch to support Linux CryptoAPI Shasi Pulijala
2008-08-08 21:09 ` Evgeniy Polyakov [this message]
2008-08-08 22:24 ` Loc Ho
2008-08-09 6:29 ` Evgeniy Polyakov
2008-08-11 18:53 ` Loc Ho
2008-08-11 19:53 ` Evgeniy Polyakov
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=20080808210949.GA6535@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=lho@amcc.com \
--cc=linux-crypto@vger.kernel.org \
--cc=spulijala@amcc.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