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 0/4] staging: lustre: small recent fixes for LNet/libcfs
Date: Mon, 9 May 2016 10:53:44 -0400 [thread overview]
Message-ID: <1462805628-23403-1-git-send-email-jsimmons@infradead.org> (raw)
Here are various fixes and improvements for the libcfs
and LNet layer. Two memory leaks fixed as well as adding
container support for the ko2iblnd driver. Lastly handle
the lower limit of the mlx5 driver for cap.max_send_wr.
Dmitry Eremin (1):
staging: lustre: o2iblnd: limit cap.max_send_wr for MLX5
James Simmons (2):
staging: lustre: libcfs: fix memort leak in libcfs crypto layer
staging: lustre: ko2iblnd: fix memory corruption with fragments
Li Dongyang (1):
staging: lustre: o2iblnd: make rdma_create_id() support containers
.../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c | 20 +++++++++++++++-----
.../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h | 2 +-
.../staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c | 8 ++++++++
.../lustre/lnet/libcfs/linux/linux-crypto.c | 1 +
4 files changed, 25 insertions(+), 6 deletions(-)
next reply other threads:[~2016-05-09 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 14:53 James Simmons [this message]
2016-05-09 14:53 ` [PATCH 1/4] staging: lustre: o2iblnd: limit cap.max_send_wr for MLX5 James Simmons
2016-05-09 14:53 ` [PATCH 2/4] staging: lustre: o2iblnd: make rdma_create_id() support containers James Simmons
2016-05-09 14:53 ` [PATCH 3/4] staging: lustre: libcfs: fix memort leak in libcfs crypto layer James Simmons
2016-05-09 14:53 ` [PATCH 4/4] staging: lustre: ko2iblnd: fix memory corruption with fragments 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=1462805628-23403-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®