From: Danny Kukawka <danny.kukawka@bisect•de>
To: Karsten Keil <kkeil@linux-pingi•de>
Cc: Ben Hutchings <bhutchings@solarflare•com>,
Armin Schindler <mac@melware•de>,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
Karsten Keil <isdn@linux-pingi•de>
Subject: Re: [PATCH 01/16] eicon: fix -Warray-bounds warning
Date: Tue, 31 Jan 2012 18:04:19 +0100 [thread overview]
Message-ID: <201201311804.20464.danny.kukawka@bisect.de> (raw)
In-Reply-To: <20120131152534.GA14825@gw.linux-pingi.de>
On Dienstag, 31. Januar 2012, Karsten Keil wrote:
> On Mon, Jan 30, 2012 at 11:09:32PM +0000, Ben Hutchings wrote:
> > On Mon, 2012-01-30 at 23:00 +0100, Danny Kukawka wrote:
> > > Fix for a -Warray-bounds warning. mixer_notify_update() tries to
> > > write to ((CAPI_MSG *) msg)->info.facility_req.structs[3] while
> > > structs is defined as byte structs[1], define structs[1] as
> > > structs[4].
> >
> > I suspect that all the 'byte structs[1];' fields defined in that header
> > are actually variable-length arrays. In that case, there may be no
> > reasonable bound you can specify.
>
> Yes, exactely, the structs is a ASN1 coded message so it can have any len.
So, how can we get rid of the compiler warning then?
Danny
> Karsten
next prev parent reply other threads:[~2012-01-31 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1327960820-11867-1-git-send-email-danny.kukawka@bisect.de>
2012-01-30 22:00 ` [PATCH 01/16] eicon: fix -Warray-bounds warning Danny Kukawka
2012-01-30 23:09 ` Ben Hutchings
2012-01-31 15:25 ` Karsten Keil
2012-01-31 17:04 ` Danny Kukawka [this message]
2012-02-01 9:04 ` David Laight
2012-02-01 12:52 ` Danny Kukawka
2012-02-02 18:25 ` Karsten Keil
2012-01-30 22:00 ` [PATCH 11/16] ath5k: make ath5k_modparam_no_hw_rfkill_switch real Danny Kukawka
2012-01-30 22:11 ` Jiri Slaby
[not found] ` <4F2715A7.9030101-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30 23:09 ` Danny Kukawka
2012-01-30 22:00 ` [PATCH 14/16] hamradio: fix incompatible pointer in module parameter Danny Kukawka
2012-02-01 19:40 ` David Miller
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=201201311804.20464.danny.kukawka@bisect.de \
--to=danny.kukawka@bisect$(echo .)de \
--cc=bhutchings@solarflare$(echo .)com \
--cc=isdn@linux-pingi$(echo .)de \
--cc=kkeil@linux-pingi$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mac@melware$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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