linux-kernel - Re: [PATCH 1/1] misc/vmw_vmci: fix filling of the msg and msg_payload in dg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2024011013-lucid-try-0119@gregkh>
Date: Wed, 10 Jan 2024 11:52:26 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: kovalev@...linux.org
Cc: bryantan@...are.com, vdasa@...are.com, pv-drivers@...are.com,
	arnd@...db.de, linux-kernel@...r.kernel.org, nickel@...linux.org,
	oficerovas@...linux.org, dutyrok@...linux.org
Subject: Re: [PATCH 1/1] misc/vmw_vmci: fix filling of the msg and
 msg_payload in dg_info struct

On Wed, Jan 10, 2024 at 01:40:42PM +0300, kovalev@...linux.org wrote:
> From: Vasiliy Kovalev <kovalev@...linux.org>
> 
> Fix "detected field-spanning write" of memcpy warning that is issued by
> the tracking mechanism __fortify_memcpy_chk, added 2021-04-20
> (f68f2ff91512c199ec24883001245912afc17873 fortify: Detect struct member overflows in memcpy() at compile-time)
> 
> Fixes: a110b7ebb9c674 ("VMCI: datagram implementation.")
> Signed-off-by: Vasiliy Kovalev <kovalev@...linux.org>
> ---
>  drivers/misc/vmw_vmci/vmci_datagram.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/misc/vmw_vmci/vmci_datagram.c b/drivers/misc/vmw_vmci/vmci_datagram.c
> index f50d22882476f9..27853b31e288b1 100644
> --- a/drivers/misc/vmw_vmci/vmci_datagram.c
> +++ b/drivers/misc/vmw_vmci/vmci_datagram.c
> @@ -234,7 +234,10 @@ static int dg_dispatch_as_host(u32 context_id, struct vmci_datagram *dg)
>  
>  			dg_info->in_dg_host_queue = true;
>  			dg_info->entry = dst_entry;
> -			memcpy(&dg_info->msg, dg, dg_size);
> +			memcpy(&dg_info->msg, dg, VMCI_DG_HEADERSIZE);
> +			if (dg->payload_size) {
> +				memcpy(dg_info->msg_payload, VMCI_DG_PAYLOAD(dg), dg->payload_size);
> +			}
>  
>  			INIT_WORK(&dg_info->work, dg_delayed_dispatch);
>  			schedule_work(&dg_info->work);
> @@ -377,7 +380,10 @@ int vmci_datagram_invoke_guest_handler(struct vmci_datagram *dg)
>  
>  		dg_info->in_dg_host_queue = false;
>  		dg_info->entry = dst_entry;
> -		memcpy(&dg_info->msg, dg, VMCI_DG_SIZE(dg));
> +		memcpy(&dg_info->msg, dg, VMCI_DG_HEADERSIZE);
> +		if (dg->payload_size) {
> +			memcpy(dg_info->msg_payload, VMCI_DG_PAYLOAD(dg), dg->payload_size);
> +		}
>  
>  		INIT_WORK(&dg_info->work, dg_delayed_dispatch);
>  		schedule_work(&dg_info->work);
> -- 
> 2.33.8
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch contains warnings and/or errors noticed by the
  scripts/checkpatch.pl tool.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot