From: John Johansen <john.johansen@canonical.com>
To: behanw@converseincode.com, agk@redhat.com, clm@fb.com,
davem@davemloft.net, dm-devel@redhat.com, fabf@skynet.be,
herbert@gondor.apana.org.au, jbacik@fb.com, snitzer@redhat.com
Cc: akpm@linux-foundation.org, james.l.morris@oracle.com,
linux-btrfs@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-security-module@vger.kernel.org, neilb@suse.de,
serge@hallyn.com, torvalds@linux-foundation.org,
"Vinícius Tinti" <viniciustinti@gmail.com>,
"Jan-Simon Möller" <dl9pf@gmx.de>,
"Mark Charlebois" <charlebm@gmail.com>
Subject: Re: [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
Date: Tue, 02 Sep 2014 16:16:33 -0700 [thread overview]
Message-ID: <54064FD1.6060900@canonical.com> (raw)
In-Reply-To: <1409697153-7006-6-git-send-email-behanw@converseincode.com>
On 09/02/2014 03:32 PM, behanw@converseincode.com wrote:
> From: Vinícius Tinti <viniciustinti@gmail.com>
>
> Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
> compliant equivalent. This is the original VLAIS struct.
>
> struct {
> struct shash_desc shash;
> char ctx[crypto_shash_descsize(apparmor_tfm)];
> } desc;
>
> This patch instead allocates the appropriate amount of memory using an
> char array.
>
> The new code can be compiled with both gcc and clang.
>
> struct shash_desc contains a flexible array member member ctx declared with
> CRYPTO_MINALIGN_ATTR, so sizeof(struct shash_desc) aligns the beginning
> of the array declared after struct shash_desc with long long.
>
> No trailing padding is required because it is not a struct type that can
> be used in an array.
>
> The CRYPTO_MINALIGN_ATTR is required so that desc is aligned with long long
> as would be the case for a struct containing a member with
> CRYPTO_MINALIGN_ATTR.
>
> Signed-off-by: Jan-Simon Möller <dl9pf@gmx.de>
> Signed-off-by: Behan Webster <behanw@converseincode.com>
> Signed-off-by: Vinícius Tinti <viniciustinti@gmail.com>
> Signed-off-by: Mark Charlebois <charlebm@gmail.com>
I'm fine with this, do you want me to pull it into my tree for our next push
or do you want this all to go together as a set?
Acked-by: John Johansen <john.johansen@canonical.com>
> ---
> security/apparmor/crypto.c | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/security/apparmor/crypto.c b/security/apparmor/crypto.c
> index 532471d..62b32e7 100644
> --- a/security/apparmor/crypto.c
> +++ b/security/apparmor/crypto.c
> @@ -32,10 +32,9 @@ unsigned int aa_hash_size(void)
> int aa_calc_profile_hash(struct aa_profile *profile, u32 version, void *start,
> size_t len)
> {
> - struct {
> - struct shash_desc shash;
> - char ctx[crypto_shash_descsize(apparmor_tfm)];
> - } desc;
> + char desc[sizeof(struct shash_desc)
> + + crypto_shash_descsize(apparmor_tfm)] CRYPTO_MINALIGN_ATTR;
> + struct shash_desc *shash = (struct shash_desc *)desc;
> int error = -ENOMEM;
> u32 le32_version = cpu_to_le32(version);
>
> @@ -46,19 +45,19 @@ int aa_calc_profile_hash(struct aa_profile *profile, u32 version, void *start,
> if (!profile->hash)
> goto fail;
>
> - desc.shash.tfm = apparmor_tfm;
> - desc.shash.flags = 0;
> + shash->tfm = apparmor_tfm;
> + shash->flags = 0;
>
> - error = crypto_shash_init(&desc.shash);
> + error = crypto_shash_init(shash);
> if (error)
> goto fail;
> - error = crypto_shash_update(&desc.shash, (u8 *) &le32_version, 4);
> + error = crypto_shash_update(shash, (u8 *) &le32_version, 4);
> if (error)
> goto fail;
> - error = crypto_shash_update(&desc.shash, (u8 *) start, len);
> + error = crypto_shash_update(shash, (u8 *) start, len);
> if (error)
> goto fail;
> - error = crypto_shash_final(&desc.shash, profile->hash);
> + error = crypto_shash_final(shash, profile->hash);
> if (error)
> goto fail;
>
>
next prev parent reply other threads:[~2014-09-02 23:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 22:32 [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM behanw
2014-09-02 22:32 ` [PATCH RFC 1/6] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt behanw
2014-09-02 22:32 ` behanw
2014-09-02 22:32 ` [PATCH RFC 2/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c behanw
2014-09-02 22:32 ` behanw
2014-09-02 22:32 ` [PATCH RFC 3/6] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c behanw
2014-09-02 22:32 ` [PATCH RFC 4/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c behanw
2014-09-02 22:32 ` behanw
2014-09-02 22:32 ` [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS behanw
2014-09-02 22:32 ` behanw
2014-09-02 23:16 ` John Johansen [this message]
2014-09-02 23:26 ` Behan Webster
2014-09-02 23:31 ` [PATCH v2] " behanw
2014-09-02 22:32 ` [PATCH RFC 6/6] btrfs: " behanw
2014-09-02 22:32 ` behanw
2014-09-02 23:01 ` [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Marcel Holtmann
2014-09-02 23:04 ` Jan-Simon Möller
2014-09-02 23:07 ` Behan Webster
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=54064FD1.6060900@canonical.com \
--to=john.johansen@canonical.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=dl9pf@gmx.de \
--cc=dm-devel@redhat.com \
--cc=fabf@skynet.be \
--cc=herbert@gondor.apana.org.au \
--cc=james.l.morris@oracle.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=neilb@suse.de \
--cc=serge@hallyn.com \
--cc=snitzer@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=viniciustinti@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.