linux-kernel - Re: most users of msleep

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: <1160578415.3000.381.camel@laptopd505.fenrus.org>
Date:	Wed, 11 Oct 2006 16:53:35 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Pierre Ossman <drzeus-list@...eus.cx>
Cc:	Matthew Wilcox <matthew@....cx>,
	Amol Lad <amol@...ismonetworks.com>,
	kernel Janitors <kernel-janitors@...ts.osdl.org>,
	linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: most users of msleep_interruptible are broken

On Wed, 2006-10-11 at 16:20 +0200, Pierre Ossman wrote:
> Matthew Wilcox wrote:
> > 
> > They clearly don't care about exactness; they msleep_interruptible and
> > throw away the return value, so they don't know how long they slept
> > before they got a signal.
> > 
> 
> It's broken then. That delay function should delay at least the amount
> given.


if you want that don't use the _interruptible variant. It's that simple.


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