mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	James Simmons <jsimmons@infradead.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	lustre <lustre-devel@lists.lustre.org>
Subject: [PATCH SERIES 4: 0/4] staging: lustre: use standard prng
Date: Mon, 18 Dec 2017 12:41:42 +1100	[thread overview]
Message-ID: <151356119565.24290.5570928075046338898.stgit@noble> (raw)

Lustre has its own internal PRNG code.
This adds nothing of value to the Linux standard prng code,
so switch over to using the standard interfaces.
This adds a few callers to add_device_randomness(), which
helps everyone, and removes unnecessary code.

Thanks,
NeilBrown


---

NeilBrown (4):
      staging: lustre: replace cfs_rand() with prandom_u32_max()
      staging: lustre: replace cfs_srand() calls with add_device_randomness().
      staging: lustre: replace cfs_get_random_bytes calls with get_random_byte()
      staging: lustre: libcfs: remove prng


 .../staging/lustre/include/linux/libcfs/libcfs.h   |   10 -
 drivers/staging/lustre/lnet/libcfs/Makefile        |    2 
 drivers/staging/lustre/lnet/libcfs/fail.c          |    2 
 drivers/staging/lustre/lnet/libcfs/prng.c          |  137 --------------------
 drivers/staging/lustre/lnet/lnet/net_fault.c       |   38 +++---
 drivers/staging/lustre/lnet/lnet/router.c          |   19 +--
 drivers/staging/lustre/lustre/include/obd_class.h  |    2 
 drivers/staging/lustre/lustre/llite/super25.c      |   17 +-
 drivers/staging/lustre/lustre/mgc/mgc_request.c    |    4 -
 .../lustre/lustre/obdclass/lustre_handles.c        |    9 -
 drivers/staging/lustre/lustre/ptlrpc/client.c      |    2 
 11 files changed, 42 insertions(+), 200 deletions(-)
 delete mode 100644 drivers/staging/lustre/lnet/libcfs/prng.c

--
Signature

             reply	other threads:[~2017-12-18  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18  1:41 NeilBrown [this message]
2017-12-18  1:41 ` [PATCH 2/4] staging: lustre: replace cfs_srand() calls with add_device_randomness() NeilBrown
2017-12-18  1:41 ` [PATCH 3/4] staging: lustre: replace cfs_get_random_bytes calls with get_random_byte() NeilBrown
2017-12-18  1:41 ` [PATCH 1/4] staging: lustre: replace cfs_rand() with prandom_u32_max() NeilBrown
2017-12-18  1:41 ` [PATCH 4/4] staging: lustre: libcfs: remove prng NeilBrown
2017-12-19  0:52 ` [lustre-devel] [PATCH SERIES 4: 0/4] staging: lustre: use standard prng Dilger, Andreas

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=151356119565.24290.5570928075046338898.stgit@noble \
    --to=neilb@suse.com \
    --cc=andreas.dilger@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jsimmons@infradead.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®