linux-kernel - Re: [PATCH 2/2] timer: Make sure TIMER_FLAG

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

Message-ID: <alpine.DEB.2.02.1403192125260.18573@ionos.tec.linutronix.de>
Date:	Wed, 19 Mar 2014 21:32:09 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Viresh Kumar <viresh.kumar@...aro.org>
cc:	Peter Zijlstra <peterz@...radead.org>,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Tejun Heo <tj@...nel.org>, Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH 2/2] timer: Make sure TIMER_FLAG_MASK bits are free in
 allocated base

On Tue, 18 Mar 2014, Viresh Kumar wrote:
> On 11 March 2014 15:56, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> >
> > Now, I was looking to migrate away the timers first but I
> > obviously shouldn't migrate the pinned timers. One way out to
> > identify PINNED timers is to mark them PINNED with the flag bits,
> > which you wouldn't allow. Can you give some other idea with which
> > I can get this solved.

Sigh, I really hoped to find some time to finish the rework, but then
you get to debug bugs, solve the problem and are rewarded with a full
inbox. Lather, rinse, repeat...

Go ahead and make the timer base aligned with more room for some bits
to tweak. The new stuff will have a flags field where stuff like
pinned is stored.

Thanks,

	tglx


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