linux-kernel - Re: [PATCH 00/11] 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131112042444.GC30281@thunk.org>
Date:	Mon, 11 Nov 2013 23:24:44 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Greg Price <price@....EDU>
Cc:	linux-kernel@...r.kernel.org, Jiri Kosina <jkosina@...e.cz>
Subject: Re: [PATCH 00/11] random: code cleanups

On Thu, Nov 07, 2013 at 06:57:25PM -0500, Greg Price wrote:
> 
> I recently read through the random number generator's code.
> This series has fixes for some minor things I spotted.
> 
> Four of the patches touch comments only.  Four simplify code without
> changing its behavior (total diffstat: 35 insertions, 73 deletions),
> and one is a trivial signedness fix.  Two patches change the locking
> and lockless concurrency control in account(), including one bugfix.
> The bug is related to the one Jiri found and fixed in May.

Hi Greg,

My apologies for not being able to get to this patch series before the
patch window opened --- this week has been crazy.  None of the changes
seem to be especially critical, and a number of the patches don't
apply cleanly to the random.git tree (some of the spelling fixes have
already been fixed, for example), which has patches queued up for the
upcoming merge window.  So I'm going to defer applying these patches
for 2.13, and I'd ask you if you'd be willing to rebase these patches
against the random.git tree, so they can be pulled in after the merge
window closes.

Thanks,

					- Ted
--
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/