From: Behan Webster <behanw@converseincode.com>
To: Chris Mason <clm@fb.com>, jbacik@fb.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
"Vinícius Tinti" <viniciustinti@gmail.com>,
"Jan-Simon Möller" <dl9pf@gmx.de>,
"Mark Charlebois" <charlebm@gmail.com>
Subject: Re: [PATCH v2] btrfs: LLVMLinux: Remove VLAIS
Date: Thu, 11 Sep 2014 16:38:25 -0500 [thread overview]
Message-ID: <54121651.50004@converseincode.com> (raw)
In-Reply-To: <5411B304.4000203@fb.com>
On 09/11/14 09:34, Chris Mason wrote:
>
> On 09/05/2014 06:58 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(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.
> We copied this from one of the other crypto api users, and I'm sure
> cooking up all these patches was not a great way to your afternoon.
>
> But, can I talk you into making a helper macro of some kind for this and
> putting it into the crypto api headers? Honestly this setup seems
> really error prone.
You're not the only person to ask for this. I've got one already coded
up based on suggestions from tglx.
I've regenerated all the patches. I will resubmit soon.
Will fix.
Behan
--
Behan Webster
behanw@converseincode.com
prev parent reply other threads:[~2014-09-11 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 22:58 [PATCH v2] btrfs: LLVMLinux: Remove VLAIS behanw
2014-09-11 14:34 ` Chris Mason
2014-09-11 21:38 ` Behan Webster [this message]
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=54121651.50004@converseincode.com \
--to=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=clm@fb.com \
--cc=dl9pf@gmx.de \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).