linux-kernel - Re: [patch 03/13] GRU - dynamic allocation of kernel contexts

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: <20090410172243.d60a43d5.akpm@linux-foundation.org>
Date:	Fri, 10 Apr 2009 17:22:43 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jack Steiner <steiner@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [patch 03/13] GRU - dynamic allocation of kernel contexts

On Fri, 10 Apr 2009 08:24:18 -0500
Jack Steiner <steiner@....com> wrote:

> +			mutex_unlock(&gts->ts_ctxlock);
> +			set_current_state(TASK_INTERRUPTIBLE);
>  			schedule_timeout(GRU_ASSIGN_DELAY);  /* true hack ZZZ */

OK...  But if the calling task has signal_pending(), the
schedule_timeout() will return immediately.

If that's a problem then perhaps use plain old msleep()?
--
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/