netdev - Re: [linux-pm] QUESTION: How to fix race between .suspend routine and watchdog timer

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]

Date:	Sun, 28 Oct 2007 21:19:05 +0200
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	linux-pm@...ts.linux-foundation.org
Subject: Re: [linux-pm] QUESTION: How to fix race between .suspend routine and watchdog timer

On Sunday 28 October 2007 00:24:10 Alan Stern wrote:
> On Sat, 27 Oct 2007, Maxim Levitsky wrote:
> 
> > > Use del_timer_sync().  It guarantees that when it returns, the timer 
> > > will be stopped and the timer routine will no longer be running on any 
> > > CPU.
> > > 
> > Even if the timer re-enables itself, are you sure?
> 
> Last time I looked at the source code, that's what it did.  I'll look
> again...  Yep, it still does.  It checks to see if the timer routine is
> currently running; if so then it waits a little while and tries again.
> 
> Alan Stern
> 
> 

Thanks, a lot,
	Best regards,
		Maxim Levitsky
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html