public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 10 Jan 2024 11:54:42 +0100	[thread overview]
Message-ID: <2024011040-unlaced-yo-yo-ff76@gregkh> (raw)
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

  parent reply	other threads:[~2024-01-10 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 10:40 [PATCH 0/1] misc/vmw_vmci: fix filling of the msg and msg_payload in dg_info struct kovalev
2024-01-10 10:40 ` [PATCH 1/1] " kovalev
2024-01-10 10:52   ` Greg KH
2024-01-10 10:54   ` Greg KH [this message]
2024-01-10 10:53 ` [PATCH 0/1] " Greg KH
2024-01-10 11:47   ` kovalev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024011040-unlaced-yo-yo-ff76@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=bryantan@vmware.com \
    --cc=dutyrok@altlinux.org \
    --cc=kovalev@altlinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickel@altlinux.org \
    --cc=oficerovas@altlinux.org \
    --cc=pv-drivers@vmware.com \
    --cc=vdasa@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox