Re: [PATCH] FUTEX: one more return .

Ok ..


On Thu, 16 Feb 2006, Ulrich Drepper wrote:

On 2/16/06, Daniel Walker <[email protected]> wrote:

Continue the theme of returns .

No, that's wrong.  I got Ingo to remove this code and he documented it:

=====
- race fix: do not bail out in the list walk when the list_op_pending
  pointer cannot be followed by the kernel - another userspace thread
  may have already destroyed the mutex (and unmapped it), before this
  thread had a chance to clear the field.
=====

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

---

• References:
  • [PATCH] FUTEX: one more return .
    • From: Daniel Walker <[email protected]>
  • Re: [PATCH] FUTEX: one more return .
    • From: Ulrich Drepper <[email protected]>

• Prev by Date: Re: (pspace,pid) vs true pid virtualization
• Next by Date: lru_list_lock in 2.4.x
• Previous by thread: Re: [PATCH] FUTEX: one more return .
• Next by thread: kernel oops: trying to mount a corrupted xfs partition (2.6.16-rc3)
• 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]