crypto: jitterentropy - remove timekeeping_valid_for_hres
authorStephan Mueller <smueller@chronox.de>
Wed, 27 May 2015 11:50:12 +0000 (13:50 +0200)
committerHerbert Xu <herbert@gondor.apana.org.au>
Thu, 28 May 2015 03:23:21 +0000 (11:23 +0800)
The patch removes the use of timekeeping_valid_for_hres which is now
marked as internal for the time keeping subsystem. The jitterentropy
does not really require this verification as a coarse timer (when
random_get_entropy is absent) is discovered by the initialization test
of jent_entropy_init, which would cause the jitter rng to not load in
that case.

Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Stephan Mueller <smueller@chronox.de>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto/jitterentropy.c

index 1ebe58a266190d18f60b469ffa09205e46eb2478..a60147e4bb3fc2664112170ce79f79fe6c2e3679 100644 (file)
@@ -131,9 +131,6 @@ static inline void jent_get_nstime(__u64 *out)
         * and are registered with clocksource_register()
         */
        if ((0 == tmp) &&
-#ifndef MODULE
-          (0 == timekeeping_valid_for_hres()) &&
-#endif
           (0 == __getnstimeofday(&ts))) {
                tmp = ts.tv_sec;
                tmp = tmp << 32;