From: Martin Wirth <martin.wirth@dlr.de>
To: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Futex Asynchronous Interface
Date: Thu, 06 Jun 2002 18:08:36 +0200 [thread overview]
Message-ID: <3CFF8904.9010703@dlr.de> (raw)
Hi Rusty,
>if (this->page == page && this->offset == offset) {
> list_del_init(i);
> tell_waiter(this);
>+ unpin_page(this->page);
> num_woken++;
> if (num_woken >= num) break;
> }
> }
> spin_unlock(&futex_lock);
>+ unpin_page(page);
> return num_woken;
If I understand right you shouldn't unpin the page if you are not sure that
all waiters for a specific (page,offset)-combination are woken up and deleted
from the waitqueue. Otherwise a second call to futex_wake may look on the wrong
hash_queue or wake the wrong waiters.
In general, I think fast userspace synchronization primitives and asynchronous
notification are different enough to keep them logically more separated.
Your double use of the hashed wait queues and sys_call make the code difficult
to grasp and thus open for subtle error.
Martin
Martin
next reply other threads:[~2002-06-06 16:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 16:08 Martin Wirth [this message]
2002-06-06 22:59 ` [PATCH] Futex Asynchronous Interface Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 7:26 Rusty Russell
2002-06-02 0:10 ` Pavel Machek
2002-06-10 6:57 ` Rusty Russell
2002-06-06 16:36 ` Linus Torvalds
2002-06-06 19:27 ` Alan Cox
2002-06-06 23:21 ` Rusty Russell
2002-06-07 8:33 ` Peter Wächtler
2002-06-08 22:28 ` Linus Torvalds
2002-06-09 9:49 ` Kai Henningsen
2002-06-09 18:09 ` Linus Torvalds
2002-06-09 19:06 ` Thunder from the hill
2002-06-10 6:39 ` Kai Henningsen
2002-06-10 7:55 ` Helge Hafting
2002-06-10 14:10 ` Thunder from the hill
2002-06-10 20:46 ` Kai Henningsen
2002-06-11 14:14 ` john slee
2002-06-10 15:11 ` Linus Torvalds
2002-06-11 15:06 ` Eric W. Biederman
2002-06-10 20:57 ` H. Peter Anvin
2002-06-09 10:07 ` Peter Wächtler
2002-06-09 17:49 ` Linus Torvalds
2002-06-07 9:06 ` Rusty Russell
2002-06-08 22:42 ` Linus Torvalds
2002-06-11 9:15 ` Rusty Russell
2002-06-11 16:53 ` Linus Torvalds
2002-06-12 5:32 ` Rusty Russell
2002-06-12 9:16 ` Peter Wächtler
2002-06-12 14:19 ` Hubertus Franke
2002-06-12 16:50 ` Peter Wächtler
2002-06-12 18:15 ` Vladimir Zidar
2002-06-12 15:39 ` Linus Torvalds
2002-06-12 16:29 ` Peter Wächtler
2002-06-12 16:52 ` Linus Torvalds
2002-06-12 17:07 ` Peter Wächtler
2002-06-12 18:32 ` Saurabh Desai
2002-06-12 20:05 ` Oliver Xymoron
2002-06-12 20:16 ` Linus Torvalds
2002-06-13 2:57 ` Rusty Russell
2002-06-13 9:37 ` Peter Wächtler
2002-06-13 9:55 ` Rusty Russell
2002-06-13 16:38 ` Gabriel Paubert
2002-06-13 16:40 ` Linus Torvalds
2002-06-13 1:32 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CFF8904.9010703@dlr.de \
--to=martin.wirth@dlr.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.