From: Christian Hesse <mail@eworm.de>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] btrfs-progs: fix compiler warning
Date: Wed, 4 Jun 2014 09:19:26 +0200 [thread overview]
Message-ID: <20140604091926.37ad5ef2@leda.localdomain> (raw)
In-Reply-To: <538EC135.6060105@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
Qu Wenruo <quwenruo@cn.fujitsu.com> on Wed, 2014/06/04 14:48:
>
> -------- Original Message --------
> Subject: [PATCH 1/1] btrfs-progs: fix compiler warning
> From: Christian Hesse <mail@eworm.de>
> To: linux-btrfs@vger.kernel.org
> Date: 2014年06月03日 19:29
> > gcc 4.9.0 gives a warning: array subscript is above array bounds
> >
> > Checking for "greater or equal" instead of just "equal" fixes this.
> >
> > Signed-off-by: Christian Hesse <mail@eworm.de>
> > ---
> > cmds-restore.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/cmds-restore.c b/cmds-restore.c
> > index 96b97e1..534a49e 100644
> > --- a/cmds-restore.c
> > +++ b/cmds-restore.c
> > @@ -169,7 +169,7 @@ again:
> > break;
> > }
> >
> > - if (level == BTRFS_MAX_LEVEL)
> > + if (level >= BTRFS_MAX_LEVEL)
> > return 1;
> >
> > slot = path->slots[level] + 1;
>
> Also I faied to reproduce the bug.
> Using gcc-4.9.0-3 from Archlinux core repo.
Exactly the same here. ;)
> It seems to be related to default gcc flags from distribution?
Probably. I did compile with optimization, so adding -O2 may do the trick:
make CFLAGS="${CFLAGS} -O2" all
--
Schoene Gruesse
Chris
O< ascii ribbon campaign
stop html mail - www.asciiribbon.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-04 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 11:29 [PATCH 1/1] btrfs-progs: fix compiler warning Christian Hesse
2014-06-03 16:52 ` David Sterba
2014-06-03 18:04 ` Christian Hesse
2014-06-04 6:48 ` Qu Wenruo
2014-06-04 7:19 ` Christian Hesse [this message]
2014-06-04 16:44 ` David Sterba
2014-06-05 8:59 ` Christian Hesse
2014-06-10 11:05 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2014-06-03 11:37 Christian Hesse
2014-06-05 8:13 Christian Hesse
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=20140604091926.37ad5ef2@leda.localdomain \
--to=mail@eworm.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).