netdev - iproute2 and kernel clock resolutions

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>] [day] [month] [year] [list]

Date:	Wed, 21 Jan 2015 14:22:36 +0100
From:	Ignacy Gawedzki <ignacy.gawedzki@...en-communications.fr>
To:	netdev@...r.kernel.org
Cc:	Patrick McHardy <kaber@...sh.net>,
	Stephen Hemminger <shemminger@...ux-foundation.org>
Subject: iproute2 and kernel clock resolutions

Hi,

While reading tc/tc_core.c, I'm having a hard time making sense of what
tc_core_init() is actually supposed to do.

It looks just as if clock_res is not filled with the correct value from
/proc/net/psched, taking into account the "compatibility hack" that follows.
AFAICT from the historical kernel Git repository, the third value in
/proc/net/psched has always been hardcoded as 1000000, so it seems that the
condition clock_res == 1000000000 is always false.  Shouldn't clock_res be
filled with the fourth value instead of the third, by any chance?

Could also anyone explain to me what this hack is actually about?

Thanks,

Ignacy

-- 
Ignacy Gawędzki
R&D Engineer
Green Communications
--
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