[Top][All Lists]

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

Re: Reauthentication implementation flaw due to EINTR

From: Samuel Thibault
Subject: Re: Reauthentication implementation flaw due to EINTR
Date: Mon, 28 Dec 2009 03:43:47 +0100
User-agent: Mutt/1.5.12-2006-07-14

Carl Fredrik Hammar, le Sun 27 Dec 2009 22:24:24 +0100, a écrit :
> OK, I think I have a vague picture of what is going on:
> ports_interrupt_self_on_port_death
> ports_interrupt_self_on_notification
> ports_interrupt_rpc_on_notification,
> which requests notification (to the same port as
> auth_server_authenticate).

But in another task (auth vs ext2fs). That's where I've still not found
what makes ext2fs return EINTR.

> When rendezvous port dies we get the notification:

Here we seemingly see ext2fs get the notification, but why?

> ports_notify_server
> ports_do_mach_notify_dead_name
> ports_dead_name
> ports_interrupt_notified_rpcs
> hurd_thread_cancel (in glibc)
> _hurdsig_abort_rpcs,
> which does some funky stuff that seems to hijack any pending RPCs
> to make them return EINTR.


reply via email to

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