[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: Sat, 26 Dec 2009 21:12:08 +0100
User-agent: Mutt/1.5.12-2006-07-14

I've checked again the result

Carl Fredrik Hammar, le Sat 26 Dec 2009 19:58:12 +0100, a écrit :
> > There is this issue as well, which I have fixed already in commit
> > 041baa80 (and indeed seen cases where it helped), but that's not enough,
> > because not only auth gets EINTR here and can fix things, but ext2fs
> > also gets an EINTR but can't able to restart the call in iohelp_reauth
> > since the rendez-vous port is dead and thus gets EINVAL.
> Why does this happen?

I don't know, but I know for sure that auth_server_authenticate returns
EINTR in ext2fs (and next call returns EINVAL), even if auth never
returned EINTR.

> I can't find any setup code for getting interrupts like in auth.  Is
> it perhaps a feature of MIG or Mach?



reply via email to

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