linux-kernel - [PATCH v2 0/9] random: code cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Nov 2013 03:07:06 -0500
From:	Greg Price <price@....EDU>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	linux-kernel@...r.kernel.org, Jiri Kosina <jkosina@...e.cz>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: [PATCH v2 0/9] random: code cleanups

This series has my cleanups rebased onto the random.git tree, at
v3.11-20-g392a546.

Four of the patches touch comments only.  Three simplify code without
changing its behavior (total diffstat: 32 insertions, 64 deletions).
One drops a use of the lock where it doesn't now protect anything,
and one tightens slightly a bound on a sysctl value to avoid a
pathological case.

The bugfix that was in v1 was taken care of by Peter in a283b5c45
("random: allow fractional bits to be tracked").

Cheers,
Greg

Greg Price (9):
  random: fix typos / spelling errors in comments
  random: fix comment on proc_do_uuid
  random: fix description of get_random_bytes
  random: simplify loop in random_read
  random: fix comment on "account"
  random: simplify accounting logic
  random: forget lock in lockless accounting
  random: tighten bound on random_read_wakeup_thresh
  random: simplify accounting code

 drivers/char/random.c | 144 +++++++++++++++++++++-----------------------------
 1 file changed, 60 insertions(+), 84 deletions(-)

-- 
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/