commit-hurd
[Top][All Lists]
Advanced

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

[SCM] GNU Mach branch, master, updated. v1.8-652-g2e6b257f


From: Samuel Thibault
Subject: [SCM] GNU Mach branch, master, updated. v1.8-652-g2e6b257f
Date: Mon, 12 Jun 2023 01:57:02 -0400 (EDT)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Mach".

The branch, master has been updated
       via  2e6b257f39ab90938ac9d425629cdf0897a47e48 (commit)
      from  f09a574a331527ccebdef88d5cc2e2c45fa072b4 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 2e6b257f39ab90938ac9d425629cdf0897a47e48
Author: Flavio Cruz <flaviocruz@gmail.com>
Date:   Mon Jun 12 00:42:06 2023 -0400

    copyinmsg: allow for the last message element to have msgt_number = 0.
    
    When copying messages from user space, some messages may have
    mach_msg_type_t with msgt_number = 0 and no data after. This is a valid
    message and we want to allow that.
    
    I found this bug when testing "[PATCH gnumach] Update the
    64bit RPC ABI to be simpler" and attempting to run a basic Hurd x86_64 that 
can start a
    bash shell. When mach_msg_type_long_t is the same size as
    mach_msg_type_t this bug happens quite frequently and prevents the
    system from starting properly.
    Message-Id: <ZIaiHnfrv6Y9hEel@jupiter.lan>

-----------------------------------------------------------------------

Summary of changes:
 x86_64/copy_user.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)


hooks/post-receive
-- 
GNU Mach



reply via email to

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