[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024011040-unlaced-yo-yo-ff76@gregkh>
Date: Wed, 10 Jan 2024 11:54:42 +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)
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
Powered by blists - more mailing lists