[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH glibc v2 26/34] hurd: Remove __hurd_local_reply_port
From: |
Samuel Thibault |
Subject: |
Re: [RFC PATCH glibc v2 26/34] hurd: Remove __hurd_local_reply_port |
Date: |
Sat, 15 Apr 2023 09:42:00 +0200 |
User-agent: |
NeoMutt/20170609 (1.8.3) |
Sergey Bugaev, le sam. 15 avril 2023 10:34:46 +0300, a ecrit:
> If you really want to deallocate and reset the current reply port, you
> need to do the dance like sigreturn does:
>
> mach_port_t reply_port = THREAD_GETMEM (THREAD_SELF, reply_port);
> THREAD_SETMEM (THREAD_SELF, MACH_PORT_DEAD);
> (void) __mach_port_mod_refs (... reply_port ...);
> THREAD_SETMEM (THREAD_SELF, MACH_PORT_NULL);
Ok.
> Maybe there should be a build step that checks that nothing unexpected
> gets pulled in, and that nothing system-dependent is ever accessed
> other than through dl-sysdep.
That can be best, yes.
Samuel
- Re: [RFC PATCH glibc 26/34] hurd: Remove __hurd_local_reply_port, (continued)
- Re: [RFC PATCH glibc 26/34] hurd: Remove __hurd_local_reply_port, Sergey Bugaev, 2023/04/11
- Re: [RFC PATCH glibc v2 26/34] hurd: Remove __hurd_local_reply_port, Samuel Thibault, 2023/04/14
- Re: [RFC PATCH glibc v2 26/34] hurd: Remove __hurd_local_reply_port, Sergey Bugaev, 2023/04/14
- Re: [RFC PATCH glibc v2 26/34] hurd: Remove __hurd_local_reply_port, Samuel Thibault, 2023/04/15
- Re: [RFC PATCH glibc v2 26/34] hurd: Remove __hurd_local_reply_port, Sergey Bugaev, 2023/04/15
- Re: [RFC PATCH glibc v2 26/34] hurd: Remove __hurd_local_reply_port,
Samuel Thibault <=