* [PATCH 00/15] gcc-10 warning fixes
@ 2020-04-30 21:30 Arnd Bergmann
2020-04-30 21:30 ` [PATCH 15/15] nvme: avoid gcc-10 zero-length-bounds warning Arnd Bergmann
0 siblings, 1 reply; 3+ messages in thread
From: Arnd Bergmann @ 2020-04-30 21:30 UTC (permalink / raw)
To: linux-kernel
Cc: linux-wireless, Bob Copeland, Alexei Starovoitov,
Amitkumar Karwar, netfilter-devel, netdev, Mikulas Patocka,
linux-scsi, Christoph Hellwig, Herbert Xu, Daniel Borkmann,
James Smart, ath10k, coreteam, Jakub Kicinski, Pablo Neira Ayuso,
linux-media, Johannes Berg, Intel Linux Wireless,
James E.J. Bottomley, Jens Axboe, linux-nvme,
Mauro Carvalho Chehab, Kalle Valo, Neil Horman,
Martin K. Petersen, Greg Kroah-Hartman, linux-usb,
Florian Westphal, linux-karma-devel, Arnd Bergmann, linux-crypto,
Jan Kara, bpf, David S. Miller
Here are a couple of fixes for warnings introduced with gcc-10.
If you wish to reproduce these, you can find the compiler I used
at [1].
If you like the fixes, please apply them directly into maintainer
trees. I expect that we will also need them to be backported
into stable kernels later.
I disabled -Wrestrict on gcc in my local test tree, but with
the patches from this series and the ones I have already sent,
I see no gcc-10 specific warnings in linux-next when doing
many randconfig builds for arm/arm64/x86.
Arnd
Arnd Bergmann (15):
crypto - Avoid free() namespace collision
iwlwifi: mvm: fix gcc-10 zero-length-bounds warning
mwifiex: avoid -Wstringop-overflow warning
ath10k: fix gcc-10 zero-length-bounds warnings
bpf: avoid gcc-10 stringop-overflow warning
netfilter: conntrack: avoid gcc-10 zero-length-bounds warning
drop_monitor: work around gcc-10 stringop-overflow warning
usb: ehci: avoid gcc-10 zero-length-bounds warning
udf: avoid gcc-10 zero-length-bounds warnings
hpfs: avoid gcc-10 zero-length-bounds warning
omfs: avoid gcc-10 stringop-overflow warning
media: s5k5baf: avoid gcc-10 zero-length-bounds warning
scsi: sas: avoid gcc-10 zero-length-bounds warning
isci: avoid gcc-10 zero-length-bounds warning
nvme: avoid gcc-10 zero-length-bounds warning
crypto/lrw.c | 6 +--
crypto/xts.c | 6 +--
drivers/media/i2c/s5k5baf.c | 4 +-
drivers/net/wireless/ath/ath10k/htt.h | 4 +-
.../net/wireless/intel/iwlwifi/fw/api/tx.h | 14 +++----
.../net/wireless/marvell/mwifiex/sta_cmd.c | 39 ++++++++-----------
drivers/nvme/host/fc.c | 2 +-
drivers/scsi/aic94xx/aic94xx_tmf.c | 4 +-
drivers/scsi/isci/task.h | 7 ++--
drivers/scsi/libsas/sas_task.c | 3 +-
fs/hpfs/anode.c | 7 +++-
fs/omfs/file.c | 12 +++---
fs/omfs/omfs_fs.h | 2 +-
fs/udf/ecma_167.h | 2 +-
fs/udf/super.c | 2 +-
include/linux/filter.h | 6 +--
include/linux/usb/ehci_def.h | 12 ++++--
include/net/netfilter/nf_conntrack.h | 2 +-
net/core/drop_monitor.c | 11 ++++--
net/netfilter/nf_conntrack_core.c | 4 +-
20 files changed, 76 insertions(+), 73 deletions(-)
[1] https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/10.0.20200413/
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Kalle Valo <kvalo@codeaurora.org>
Cc: Johannes Berg <johannes.berg@intel.com>
Cc: Intel Linux Wireless <linuxwifi@intel.com>
Cc: Amitkumar Karwar <amitkarwar@gmail.com>
Cc: James Smart <james.smart@broadcom.com>
Cc: Jens Axboe <axboe@fb.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: Bob Copeland <me@bobcopeland.com>
Cc: Jan Kara <jack@suse.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>
Cc: Jakub Kicinski <kuba@kernel.org>
Cc: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-media@vger.kernel.org
Cc: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Cc: netdev@vger.kernel.org
Cc: linux-nvme@lists.infradead.org
Cc: linux-scsi@vger.kernel.org
Cc: linux-karma-devel@lists.sourceforge.net
Cc: bpf@vger.kernel.org
Cc: linux-usb@vger.kernel.org
Cc: netfilter-devel@vger.kernel.org
Cc: coreteam@netfilter.org
--
2.26.0
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH 15/15] nvme: avoid gcc-10 zero-length-bounds warning
2020-04-30 21:30 [PATCH 00/15] gcc-10 warning fixes Arnd Bergmann
@ 2020-04-30 21:30 ` Arnd Bergmann
2020-05-01 7:32 ` Christoph Hellwig
0 siblings, 1 reply; 3+ messages in thread
From: Arnd Bergmann @ 2020-04-30 21:30 UTC (permalink / raw)
To: linux-kernel, James Smart, Keith Busch, Jens Axboe,
Christoph Hellwig, Sagi Grimberg, Israel Rukshin, Max Gurtovoy
Cc: linux-nvme, Hannes Reinecke, Arnd Bergmann, Ming Lei
When CONFIG_ARCH_NO_SG_CHAIN is set, op->sgl[0] cannot be dereferenced,
as gcc-10 now points out:
drivers/nvme/host/fc.c: In function 'nvme_fc_init_request':
drivers/nvme/host/fc.c:1774:29: warning: array subscript 0 is outside the bounds of an interior zero-length array 'struct scatterlist[0]' [-Wzero-length-bounds]
1774 | op->op.fcp_req.first_sgl = &op->sgl[0];
| ^~~~~~~~~~~
drivers/nvme/host/fc.c:98:21: note: while referencing 'sgl'
98 | struct scatterlist sgl[NVME_INLINE_SG_CNT];
| ^~~
I don't know if this is a legitimate warning or a false-positive.
If this is just a false alarm, the warning is easily suppressed
by interpreting the array as a pointer.
Fixes: b1ae1a238900 ("nvme-fc: Avoid preallocating big SGL for data")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
drivers/nvme/host/fc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c
index 887537d1243f..b7ecda48d597 100644
--- a/drivers/nvme/host/fc.c
+++ b/drivers/nvme/host/fc.c
@@ -1771,7 +1771,7 @@ nvme_fc_init_request(struct blk_mq_tag_set *set, struct request *rq,
res = __nvme_fc_init_request(ctrl, queue, &op->op, rq, queue->rqcnt++);
if (res)
return res;
- op->op.fcp_req.first_sgl = &op->sgl[0];
+ op->op.fcp_req.first_sgl = op->sgl;
op->op.fcp_req.private = &op->priv[0];
nvme_req(rq)->ctrl = &ctrl->ctrl;
return res;
--
2.26.0
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 15/15] nvme: avoid gcc-10 zero-length-bounds warning
2020-04-30 21:30 ` [PATCH 15/15] nvme: avoid gcc-10 zero-length-bounds warning Arnd Bergmann
@ 2020-05-01 7:32 ` Christoph Hellwig
0 siblings, 0 replies; 3+ messages in thread
From: Christoph Hellwig @ 2020-05-01 7:32 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Sagi Grimberg, Israel Rukshin, linux-kernel, linux-nvme,
James Smart, Jens Axboe, Hannes Reinecke, Keith Busch,
Max Gurtovoy, Ming Lei, Christoph Hellwig
On Thu, Apr 30, 2020 at 11:30:57PM +0200, Arnd Bergmann wrote:
> When CONFIG_ARCH_NO_SG_CHAIN is set, op->sgl[0] cannot be dereferenced,
> as gcc-10 now points out:
>
> drivers/nvme/host/fc.c: In function 'nvme_fc_init_request':
> drivers/nvme/host/fc.c:1774:29: warning: array subscript 0 is outside the bounds of an interior zero-length array 'struct scatterlist[0]' [-Wzero-length-bounds]
> 1774 | op->op.fcp_req.first_sgl = &op->sgl[0];
> | ^~~~~~~~~~~
> drivers/nvme/host/fc.c:98:21: note: while referencing 'sgl'
> 98 | struct scatterlist sgl[NVME_INLINE_SG_CNT];
> | ^~~
>
> I don't know if this is a legitimate warning or a false-positive.
> If this is just a false alarm, the warning is easily suppressed
> by interpreting the array as a pointer.
This looks like a surpression to be, but then again I find the new
code actually cleaner, so I'm fine with it :)
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-05-01 7:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-30 21:30 [PATCH 00/15] gcc-10 warning fixes Arnd Bergmann
2020-04-30 21:30 ` [PATCH 15/15] nvme: avoid gcc-10 zero-length-bounds warning Arnd Bergmann
2020-05-01 7:32 ` Christoph Hellwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).