Existing MiG does not support untyped messages and the Hurd will
continue to use typed messages for the foreseeable future.
---
hurd/hurdfault.c | 4 ---
hurd/intr-msg.c| 69 --
mach/msg-destroy.c | 64 --
Applied, thanks!
Flavio Cruz, le sam. 18 nov. 2023 18:18:44 -0500, a ecrit:
> The `ty` pointer is only set at the end of the loop so that
> `msgtl_header.msgt_inline` and `msgtl_header.msgt_deallocate` remain
> valid. Also, when deallocating memory, we use the length from the
> message directly
Applied, thanks!
Flavio Cruz, le sam. 18 nov. 2023 18:24:11 -0500, a ecrit:
> ---
> libfshelp/start-translator-long.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libfshelp/start-translator-long.c
> b/libfshelp/start-translator-long.c
> index 0d6c574..0b16e7d 100644
---
libfshelp/start-translator-long.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libfshelp/start-translator-long.c
b/libfshelp/start-translator-long.c
index 0d6c574..0b16e7d 100644
--- a/libfshelp/start-translator-long.c
+++ b/libfshelp/start-translator-long.c
@@ -110,7
The `ty` pointer is only set at the end of the loop so that
`msgtl_header.msgt_inline` and `msgtl_header.msgt_deallocate` remain
valid. Also, when deallocating memory, we use the length from the
message directly rather than hard coding mach_port_t since we want to
deallocate any kind of OOL data.