netdev - Re: [NET] random : secure_tcp_sequence_number should not assume CONFIG_KTIME

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, 13 Nov 2007 21:13:16 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	dada1@...mosbay.com
Cc:	netdev@...r.kernel.org, kaber@...sh.net, stable@...nel.org
Subject: Re: [NET] random : secure_tcp_sequence_number should not assume
 CONFIG_KTIME_SCALAR

From: Eric Dumazet <dada1@...mosbay.com>
Date: Tue, 13 Nov 2007 14:41:19 +0100

> I discovered one other incorrect use of .tv64 (coming from me, I must 
> confess)
> 
> I guess this patch is  needed for 2.6.24 and stable (2.6.22 & 2.6.23)
 ...
> [NET] random : secure_tcp_sequence_number should not assume 
> CONFIG_KTIME_SCALAR

Applied thanks Eric, I'll queue it up for -stable too.

Perhaps ktime_t->tv64 should be renamed to "->__tv64" or
similar to prevent future mistakes like this.  Only
the ktime implementation should be touching that thing.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html