linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: warning: division by zero
Date: Wed, 14 Feb 2018 01:39:09 +0100	[thread overview]
Message-ID: <20180214003907.2ym6hgjp3vzptw53@ltop.local> (raw)
In-Reply-To: <8708546d-78da-622d-bc26-d2a0cf40cda4@infradead.org>

On Tue, Feb 13, 2018 at 04:26:04PM -0800, Randy Dunlap wrote:
> In Linux kernel, we get that message 2 times (in x86_64 allmodconfig):
> 
> ../fs/exofs/ore_raid.c:95:64: warning: division by zero
> ../fs/exofs/ore_raid.c:116:36: warning: division by zero
> 
> when dividing by variable sizeof_a1pa, where that is:
> 	const unsigned sizeof__a1pa = sizeof(_aab->__a1pa[0]);
> 
> which is in this struct:
> 	struct _alloc_all_bytes {
> 		struct __alloc_stripe_pages_2d {
> 			struct __stripe_pages_2d sp2d;
> 			struct __1_page_stripe _1p_stripes[pages_in_unit];
> 		} __asp2d;
> 		struct __alloc_1p_arrays {
> 			struct page *pages[group_width];
> 			struct page *scribble[group_width];
> 			char page_is_read[data_devs];
> 		} __a1pa[pages_in_unit];
> 	} *_aab;
> 
> where 'pages_in_unit' is a function parameter. So, yes, it could have a value
> of zero.
> 
> Is the warning message considered correct or useful as is?  If so, OK, no problem.

It's a division by zero, not because the parameter can be zero
but because currently sparse doesn't handle the size of VLAs which
are always considered as zero-sized.
So, no I don't consider this warning as correct and even less useful.

I have a WIP series to handle VLA's sizeof, if there is some interests
I can boost a bit its priority.

> Although I would rather see something more like:
> 	warning: variable length array on stack

That's of course something different that could indeed be quite useful.

-- Luc

  reply	other threads:[~2018-02-14  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14  0:26 warning: division by zero Randy Dunlap
2018-02-14  0:39 ` Luc Van Oostenryck [this message]
2018-02-14  0:43   ` Randy Dunlap

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=20180214003907.2ym6hgjp3vzptw53@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).