Received-SPF: pass (google.com: domain of linux-kernel+bounces-22025-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Wed, 10 Jan 2024 11:54:42 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: kovalev@altlinux.org
Cc: bryantan@vmware.com, vdasa@vmware.com, pv-drivers@vmware.com,
	arnd@arndb.de, linux-kernel@vger.kernel.org, nickel@altlinux.org,
	oficerovas@altlinux.org, dutyrok@altlinux.org
Subject: Re: [PATCH 1/1] misc/vmw_vmci: fix filling of the msg and
 msg_payload in dg_info struct
Message-ID: <2024011040-unlaced-yo-yo-ff76@gregkh>
References: <20240110104042.31865-1-kovalev@altlinux.org>
 <20240110104042.31865-2-kovalev@altlinux.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20240110104042.31865-2-kovalev@altlinux.org>

On Wed, Jan 10, 2024 at 01:40:42PM +0300, kovalev@altlinux.org wrote:
> From: Vasiliy Kovalev <kovalev@altlinux.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)

Please properly quote commits.

> Fixes: a110b7ebb9c674 ("VMCI: datagram implementation.")

It's not really a bug to be "fixed", right?  It's just a "shut up the
fortify checkers with this false-positive" type of thing.

Again, see the thread I pointed you at for this same discussion.

thanks,

greg k-h