linux-kernel - Re: kernel/timer: avoid spurious ksoftirqd wakeups (v2)

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: <alpine.DEB.2.11.1504111124020.3845@nanos>
Date:	Sat, 11 Apr 2015 11:25:49 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Luiz Capitulino <lcapitulino@...hat.com>
cc:	Marcelo Tosatti <mtosatti@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org, Rik van Riel <riel@...hat.com>
Subject: Re: kernel/timer: avoid spurious ksoftirqd wakeups (v2)

On Fri, 10 Apr 2015, Luiz Capitulino wrote:
> On Fri, 10 Apr 2015 15:09:07 -0300
> > It seems a valid solution for this interrupt is to program 
> > sched_timer to the nearest future possible. 
> 
> What about calling the timer function right there, like
> hrtimer_interrupt() does?

No, you cannot call the timer function from the enqueue path. The
caller might hold a lock which is taken in the callback as well.....

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/