linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150324154855.GQ21418@twins.programming.kicks-ass.net>
Date:	Tue, 24 Mar 2015 16:48:55 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Paweł Moll <pawel.moll@....com>,
	Adrian Hunter <adrian.hunter@...el.com>,
	Ingo Molnar <mingo@...nel.org>,
	Stephane Eranian <eranian@...gle.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	David Ahern <dsahern@...il.com>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung@...il.com>,
	Paul Mackerras <paulus@...ba.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Sonny Rao <sonnyrao@...omium.org>,
	"ak@...ux.intel.com" <ak@...ux.intel.com>, vincent.weaver@...ne.edu
Subject: Re: [RFC][PATCH 0/4] Another go at ktime_get_raw_fast_ns()

On Tue, Mar 24, 2015 at 08:20:07AM -0700, John Stultz wrote:
> On Thu, Mar 19, 2015 at 2:31 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> > Hi John,
> >
> > So yeah, I just didn't try hard enough it seems; how about this?
> 
> Yea, this looks much better!  I'll queue it up for testing and if that
> goes well include it for 4.1.

I have a few patches that depend on it, so if you're ok with it I'd like
to carry the lot. But yes please test ;-)

> > 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.
> 
> At one point it was install and never remove, but I think Thomas
> changed that awhile back, so I think your concern here is a good one.

OK, I'll try and dig around a bit on this.
--
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/