linux-kernel - feature-removal-schedule entry from 2009

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]

Message-ID: <4FFDA698.2000707@landley.net>
Date:	Wed, 11 Jul 2012 11:15:20 -0500
From:	Rob Landley <rob@...dley.net>
To:	LKML <linux-kernel@...r.kernel.org>, rgetz@...ckfin.uclinux.org,
	mpm@...enic.com
Subject: feature-removal-schedule entry from 2009

IRQF_SAMPLE_RANDOM is 3 years past its sell-by date in
feature-removal-schedule:

What:   IRQF_SAMPLE_RANDOM
Check:  IRQF_SAMPLE_RANDOM
When:   July 2009

Why:    Many of IRQF_SAMPLE_RANDOM users are technically bogus as
        entropy sources in the kernel's current entropy model. To
        resolve this, every input point to the kernel's entropy pool
        needs to better document the type of entropy source it actually
        is. This will be replaced with additional add_*_randomness
        functions in drivers/char/random.c

Who:    Robin Getz <rgetz@...ckfin.uclinux.org>
        & Matt Mackall <mpm@...enic.com>

There are 12 remaining uses under drivers/ and 14 more under arch/, the
rest of the hits look like infrastructure implementing it.

Should I run those files through bother-maintainer.pl and try to get
people to stop it, or is there a plan underway I don't know about?

Rob
-- 
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation.  Pick one.
--
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/