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]
Date:	Tue, 17 Jul 2012 21:56:09 -0700
From:	Anton Vorontsov <cbouatmailru@...il.com>
To:	Theodore Ts'o <tytso@....edu>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH 04/17] pda_power: remove IRQF_SAMPLE_RANDOM which is now
 a no-op

On Wed, Jul 18, 2012 at 12:18:20AM -0400, Theodore Ts'o wrote:
> On Tue, Jul 17, 2012 at 09:00:09PM -0700, Anton Vorontsov wrote:
> > On Tue, Jul 17, 2012 at 05:32:23PM -0400, Theodore Ts'o wrote:
> > > With the changes in the random tree, IRQF_SAMPLE_RANDOM is now a
> > > no-op; interrupt randomness is now collected unconditionally in a very
> > > low-overhead fashion; see commit 775f4b297b.  The IRQF_SAMPLE_RANDOM
> > > flag was scheduled to be removed in 2009 on the
> > > feature-removal-schedule, so this patch is preparation for the final
> > > removal of this flag.
> > > 
> > > Signed-off-by: "Theodore Ts'o" <tytso@....edu>
> > > Cc: Anton Vorontsov <cbou@...l.ru>
> > > Cc: David Woodhouse <dwmw2@...radead.org>
> > > ---
> > 
> > Applied, thanks!
> 
> My original plan was to carry the patch in the random.git tree, so
> that it only gets applied after the new random interrupt sampling
> commit has gone in.  If you carry it in your tree, then the
> /dev/random seeding for your platform will be worse until the
> random.git tree is merged in.....

Oh, I see. OK, dropped.

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru@...il.com
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ