bug-hurd
[Top][All Lists]
Advanced

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

Re: [RFC PATCH glibc 24/34] hurd: Only check for TLS initialization insi


From: Samuel Thibault
Subject: Re: [RFC PATCH glibc 24/34] hurd: Only check for TLS initialization inside rtld or in static builds
Date: Fri, 14 Apr 2023 11:31:19 +0200
User-agent: NeoMutt/20170609 (1.8.3)

Sergey Bugaev via Libc-alpha, le ven. 14 avril 2023 12:23:00 +0300, a ecrit:
> On Fri, Apr 14, 2023 at 12:12 PM Samuel Thibault
> <samuel.thibault@gnu.org> wrote:
> > Sergey Bugaev via Libc-alpha, le ven. 14 avril 2023 11:53:43 +0300, a ecrit:
> > > It's in _hurdsig_abort_rpcs, if the interrupt_operation call fails.
> > >
> > > Let's maybe not do that either? We're already making mach_msg seem to
> > > have returned EINTR, which intr-msg knows how to handle.
> >
> > Mmm, yes, but we need to make *sure* we don't re-use the port and
> > that it gets dropped at some point not too far, otherwise the
> > server will stay stuck trying to reply.
> 
> We should drop the reply port before waiting for the signal handler to
> run, since the handler may block -- is that what you're saying?

That's a kind of scenario indeed. I don't know if it's actually
exercised in the wild, but I wouldn't be surprised.

Samuel



reply via email to

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