From: James Simmons <jsimmons@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>,
James Simmons <jsimmons@infradead.org>
Subject: [PATCH 00/12] Bring the libcfs crypto code up to date
Date: Sat, 26 Mar 2016 15:40:44 -0400 [thread overview]
Message-ID: <1459021256-23857-1-git-send-email-jsimmons@infradead.org> (raw)
Several important fixes for the crypto handling are missing for
the upstream client. This work integates those missing fixes.
Andreas Dilger (12):
staging: lustre: libcfs: limit scope of libcfs_crypto.h
staging: lustre: libcfs: add documentation for cfs_crypto_hash_*()
staging: lustre: libcfs: rename some variables for crypto handling
staging: lustre: libcfs: add new definitions for cfs_crypto api
staging: lustre: libcfs: small alignment change for cfs_crypto_hash_*()
staging: lustre: libcfs: start using enum cfs_crypto_hash_alg
staging: lustre: libcfs: bug fixes for cfs_crypto_hash_final()
staging: lustre: libcfs: return proper error code for cfs_crypto_hash_speed()
staging: lustre: libcfs: allocate memory in cfs_crypto_performance_test()
staging: lustre: libcfs: print crypto performance result only on success
staging: lustre: libcfs: improve reporting error for crypto performance
staging: lustre: libcfs: calculate crypto performance using pages
.../staging/lustre/include/linux/libcfs/libcfs.h | 1 -
.../lustre/include/linux/libcfs/libcfs_crypto.h | 136 ++++------
.../lustre/lnet/libcfs/linux/linux-crypto.c | 274 +++++++++++++++-----
drivers/staging/lustre/lustre/include/obd_cksum.h | 1 +
drivers/staging/lustre/lustre/osc/osc_request.c | 5 +-
drivers/staging/lustre/lustre/ptlrpc/sec_bulk.c | 12 +-
6 files changed, 270 insertions(+), 159 deletions(-)
next reply other threads:[~2016-03-26 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 19:40 James Simmons [this message]
2016-03-26 19:40 ` [PATCH 01/12] staging: lustre: libcfs: limit scope of libcfs_crypto.h James Simmons
2016-03-26 19:40 ` [PATCH 02/12] staging: lustre: libcfs: add documentation for cfs_crypto_hash_*() James Simmons
2016-03-26 19:40 ` [PATCH 03/12] staging: lustre: libcfs: rename some variables for crypto handling James Simmons
2016-03-26 19:40 ` [PATCH 04/12] staging: lustre: libcfs: add new definitions for cfs_crypto api James Simmons
2016-03-26 19:40 ` [PATCH 05/12] staging: lustre: libcfs: small alignment change for cfs_crypto_hash_*() James Simmons
2016-03-26 19:40 ` [PATCH 06/12] staging: lustre: libcfs: start using enum cfs_crypto_hash_alg James Simmons
2016-03-26 19:40 ` [PATCH 07/12] staging: lustre: libcfs: bug fixes for cfs_crypto_hash_final() James Simmons
2016-03-26 19:40 ` [PATCH 08/12] staging: lustre: libcfs: return proper error code for cfs_crypto_hash_speed() James Simmons
2016-03-26 19:40 ` [PATCH 09/12] staging: lustre: libcfs: allocate memory in cfs_crypto_performance_test() James Simmons
2016-03-26 19:40 ` [PATCH 10/12] staging: lustre: libcfs: print crypto performance result only on success James Simmons
2016-03-26 19:40 ` [PATCH 11/12] staging: lustre: libcfs: improve reporting error for crypto performance James Simmons
2016-03-26 19:40 ` [PATCH 12/12] staging: lustre: libcfs: calculate crypto performance using pages James Simmons
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=1459021256-23857-1-git-send-email-jsimmons@infradead.org \
--to=jsimmons@infradead.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.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
all inboxes | Powered by JetHome®