[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Richard Braun
Date: Fri, 3 Aug 2012 22:52:56 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

On Fri, Aug 03, 2012 at 01:44:54PM -0700, Roland McGrath wrote:
> That's certainly not what's done currently.  hurd_thread_cancel causes
> all "interruptible" RPC stubs to return EINTR, either by preventing
> the RPC from being made or by sending interrupt_operation RPCs to
> servers.  This is the effect of the INTR_INTERFACE macro that appears
> in hurd/*.defs.  (See libc/hurd/intr-msg.c, _hurdsig_abort_rpcs, etc.)
> This is the moral equivalent to the POSIX calls that are cancellation
> points.  (The Hurd code predates the specification of pthreads by a
> few years, but it was designed according to the same concept of
> cancellation that lead to that part of the pthreads specification.)

Right, EINTR is indeed the expected error in such cases.

> I can't really imagine what issue you have in mind.  To fit with the
> convention in NPTL for extensions, it should be PTHREAD_CANCEL_POLLED_NP.
> (The "_NP" suffix indicates it's a non-POSIX feature.)

Nothing particular in mind, It's just that I initially saw this type as
being Hurd-specific, but there is no reason to tie it to the Hurd.

Richard Braun

reply via email to

[Prev in Thread] Current Thread [Next in Thread]