linux-kernel - [RFC][PATCH 0/4] Another go at ktime_get_raw_fast

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]

Date:	Thu, 19 Mar 2015 10:31:37 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	john.stultz@...aro.org, tglx@...utronix.de
Cc:	pawel.moll@....com, adrian.hunter@...el.com, mingo@...nel.org,
	eranian@...gle.com, linux-kernel@...r.kernel.org, acme@...nel.org,
	dsahern@...il.com, fweisbec@...il.com, jolsa@...hat.com,
	namhyung@...il.com, paulus@...ba.org, rostedt@...dmis.org,
	sonnyrao@...omium.org, ak@...ux.intel.com,
	vincent.weaver@...ne.edu, peterz@...radead.org
Subject: [RFC][PATCH 0/4] Another go at ktime_get_raw_fast_ns()

Hi John,

So yeah, I just didn't try hard enough it seems; how about this?

Also, I think we should double check that everything passed to
tk_setup_internals(.clock) is either static storage or RCU-sched freed,
because with the whole latch thing one CPUs (fast) access might still be
in progress while the other is freeing the clock struct.

Not sure what the lifetime rules of struct clocksource are here.

--
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/