linux-kernel - Re: clockevents_shutdown vs pending interrupt

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.1506231214490.4037@nanos>
Date:	Tue, 23 Jun 2015 12:15:52 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andriy Gapon <avg@...eBSD.org>
cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: clockevents_shutdown vs pending interrupt

On Tue, 23 Jun 2015, Andriy Gapon wrote:
> Pardon if I am asking something obvious or silly...
> 
> tick_check_new_device() has the following code:
> 
>         if (tick_is_broadcast_device(curdev)) {
>                 clockevents_shutdown(curdev);
>                 curdev = NULL;
>         }
> 
> and
> 
> void clockevents_shutdown(struct clock_event_device *dev)
> {
>         clockevents_set_mode(dev, CLOCK_EVT_MODE_SHUTDOWN);
>         dev->next_event.tv64 = KTIME_MAX;
> }
> 
> This is all done while interrupts are disabled on the current CPU.
> But what if there is already a pending interrupt from the current source?
> Is it possible that the timer interrupt would be processed by the device that
> was put in the shutdown mode?
> 
> Some context: I am experiencing exactly the same symptoms as described here
> http://thread.gmane.org/gmane.linux.kernel/1483297.  But I run a kernel where
> that bug is fixed.  And my problem happens in a VM, so it's possible that there
> are timing issues which are very unlikely on real hardware.

Can you provide a full dmesg please?

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/