[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150519063211.GA28347@gondor.apana.org.au>
Date: Tue, 19 May 2015 14:32:11 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Jaegeuk Kim <jaegeuk@...nel.org>
Cc: davem@...emloft.net, linux-crypto@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, ecryptfs@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
On Mon, May 18, 2015 at 11:24:30PM -0700, Jaegeuk Kim wrote:
>
> The call path in fs/ext4/crypto.c is:
> - writepage
> - ext4_encrypt
> - ext4_get_crypto_ctx
> - crypto_alloc_ablkcipher
>
> AFAIK, this way can achieve to reduce memory footprint gracefully.
> Just before submitting bios, fs allocates the required memory, and then end_io
> will free them in pair.
So where does the key get generated? The crypto tfm should be
allocated when you generate the key.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists