Re: most users of msleep_interruptible are broken

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.

Rgds
Pierre

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: most users of msleep_interruptible are broken
    • From: Arjan van de Ven <[email protected]>

• References:
  • [PATCH] drivers/mmc/mmc.c: Replacing yield() with a better alternative
    • From: Amol Lad <[email protected]>
  • Re: [PATCH] drivers/mmc/mmc.c: Replacing yield() with a better alternative
    • From: Arjan van de Ven <[email protected]>
  • most users of msleep_interruptible are broken
    • From: Matthew Wilcox <[email protected]>

• Prev by Date: Re: [PATCH] Remove me from maintainers for serial and mmc
• Next by Date: Re: 2.6.18 ext3 panic.
• Previous by thread: most users of msleep_interruptible are broken
• Next by thread: Re: most users of msleep_interruptible are broken
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]