netdev - Re: [PATCH] Return value from schedule()

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: <1220600440.7080.2.camel@twins.programming.kicks-ass.net>
Date:	Fri, 05 Sep 2008 09:40:40 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	Matthew Wilcox <matthew@....cx>,
	Arjan van de Ven <arjan@...radead.org>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>,
	Ben Hutchings <bhutchings@...arflare.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	linux-pci@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] Return value from schedule()

On Thu, 2008-09-04 at 12:05 -0700, Stephen Hemminger wrote:
> On Thu, 4 Sep 2008 11:48:45 -0600
> Matthew Wilcox <matthew@....cx> wrote:
> 
> > On Thu, Sep 04, 2008 at 10:30:49AM -0700, Arjan van de Ven wrote:
> > > use schedule_hrtimerout() for this (hopefully will be in 2.6.28);
> > > see this weeks LWN for an article describing it
> > 
> > OK, so something like:
> > 
> > 	struct timespec ts = { 0, 10 * 1000 };
> > 
> > 	set_task_state(TASK_INTERRUPTIBLE);
> > 	schedule_hrtimeout(&ts, HRTIMER_MODE_REL);
> > 	if (fatal_signal_pending())
> > 		return -EINTR;
> > 
> > should do the trick.
> > 
> 
> Never mind, I changed it to just yield() in revision.

Gah, not another yield in the network code we have to figure out wtf its
meant to do.



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