From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: james.smart@broadcom.com, dick.kennedy@broadcom.com,
James.Bottomley@HansenPartnership.com,
Sherry Yang <sherry.yang@oracle.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: lpfc: fix overflow build issue
Date: Thu, 22 Aug 2024 21:56:03 -0400 [thread overview]
Message-ID: <172437814913.4018943.7804520176988407566.b4-ty@oracle.com> (raw)
In-Reply-To: <20240821065131.1180791-1-sherry.yang@oracle.com>
On Tue, 20 Aug 2024 23:51:31 -0700, Sherry Yang wrote:
> Build failed while enabling "CONFIG_GCOV_KERNEL=y" and
> "CONFIG_GCOV_PROFILE_ALL=y" with following error:
>
> BUILDSTDERR: drivers/scsi/lpfc/lpfc_bsg.c: In function 'lpfc_get_cgnbuf_info':
> BUILDSTDERR: ./include/linux/fortify-string.h:114:33: error: '__builtin_memcpy' accessing 18446744073709551615 bytes at offsets 0 and 0 overlaps 9223372036854775807 bytes at offset -9223372036854775808 [-Werror=restrict]
> BUILDSTDERR: 114 | #define __underlying_memcpy __builtin_memcpy
> BUILDSTDERR: | ^
> BUILDSTDERR: ./include/linux/fortify-string.h:637:9: note: in expansion of macro '__underlying_memcpy'
> BUILDSTDERR: 637 | __underlying_##op(p, q, __fortify_size); \
> BUILDSTDERR: | ^~~~~~~~~~~~~
> BUILDSTDERR: ./include/linux/fortify-string.h:682:26: note: in expansion of macro '__fortify_memcpy_chk'
> BUILDSTDERR: 682 | #define memcpy(p, q, s) __fortify_memcpy_chk(p, q, s, \
> BUILDSTDERR: | ^~~~~~~~~~~~~~~~~~~~
> BUILDSTDERR: drivers/scsi/lpfc/lpfc_bsg.c:5468:9: note: in expansion of macro 'memcpy'
> BUILDSTDERR: 5468 | memcpy(cgn_buff, cp, cinfosz);
> BUILDSTDERR: | ^~~~~~
>
> [...]
Applied to 6.11/scsi-fixes, thanks!
[1/1] scsi: lpfc: fix overflow build issue
https://git.kernel.org/mkp/scsi/c/3417c9574e36
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2024-08-23 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 6:51 Sherry Yang
2024-08-21 17:00 ` Justin Tee
2024-08-23 1:56 ` Martin K. Petersen [this message]
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=172437814913.4018943.7804520176988407566.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sherry.yang@oracle.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
all inboxes | Powered by JetHome®