Date: Fri, 21 Nov 2003 12:40:38 +0100 (CET)
From: Krzysztof Benedyczak <golbi@mat.uni.torun.pl>
To: Jamie Lokier <jamie@shareable.org>
cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] POSIX message queues - syscalls & SIGEV_THREAD
In-Reply-To: <20031118124754.GA23333@mail.shareable.org>
Message-ID: <Pine.GSO.4.58.0311211238180.4918@ultra60>
References: <Pine.GSO.4.58.0311161546260.25475@Juliusz>
 <20031117064832.GA16597@mail.shareable.org> <Pine.GSO.4.58.0311171236420.29330@Juliusz>
 <20031117153323.GA18523@mail.shareable.org> <Pine.GSO.4.58.0311181254490.27011@Juliusz>
 <20031118124754.GA23333@mail.shareable.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 981
Lines: 25

On Tue, 18 Nov 2003, Jamie Lokier wrote:

[CUT]
> You are setting the first futex's word in userspace prior to the first
> futex wakeup, right?  Either 5 will detect that and return
> immediately, or it will reach 6 and the poll() returns immediately.
> No hole there.
>
> ( The async token passing flaw is that the _waker_ loses track of how
> many succesful wakeups it has sent; this is used by some
> implementations of fair semaphores, among other things.  That might be
> relevant to POSIX message queues but I do not see that it's relevant
> to the two futex problem you described. )
>

Thanks for information. I was wrongly assmuming that poll will block.
After checking the code - I know I have made a mistake.

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