mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Luis Pereira dos Santos - BSRSoft" <andre@bsrsoft.com.br>
To: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] fs: Small refactoring of the code in ext4 2.6.37-rc1
Date: Thu, 4 Nov 2010 16:34:26 -0700 (PDT)	[thread overview]
Message-ID: <756314.4122.qm@web110514.mail.gq1.yahoo.com> (raw)

  Hello.

This is true.
Despite having gone through all compilation and I have not noticed apparent problems, my mistake is evident in this case.

I had not realized that the side effect would really be changing variables incremented and decremented.

Thank you.

I'll think more about this type of side effect. :)


On Thu, 4 Nov 2010, André Luis Pereira dos Santos - BSRSoft wrote:

> From: Andre Luis Pereira dos Santos <andre@bsrsoft.com.br>
>
> Hi.
> Small refactoring of the code in order to make minor enhancements to critical areas.
> The notation x + 1 has been replaced by more efficient notation x + +.
>
> Signed-off-by: Andre Luis Pereira dos Santos <andre@bsrsoft.com.br>
> ---
> Signed-off-by: Andre Luis Pereira dos Santos <andre@bsrsoft.com.br>
> --- linux-2.6.37-rc1/fs/ext4/extents.c        2010-11-01 09:54:12.000000000 -0200
> +++ linux-2.6.37-rc1-patched/fs/ext4/extents.c        2010-11-04 19:54:26.000000000 -0200
> @@ -555,9 +555,9 @@ ext4_ext_binsearch(struct inode *inode,
>       while (l <= r) {
>               m = l + (r - l) / 2;
>               if (block < le32_to_cpu(m->ee_block))
> -                     r = m - 1;
> +                     r = m--;
>               else
> -                     l = m + 1;
> +                     l = m++;

These do not give identical results.

foo = bar + 1;  assigns (bar + 1) to foo.
foo = bar--;  assigns bar to foo then decrements bar.
foo = --bar;  decrements bar then assigns bar to foo.

So your change both change the value that will be assigned to 'r' and 'l'
and also modify 'm' which was not previously modified.


>               ext_debug("%p(%u):%p(%u):%p(%u) ", l, le32_to_cpu(l->ee_block),
>                               m, le32_to_cpu(m->ee_block),
>                               r, le32_to_cpu(r->ee_block));
> @@ -1557,7 +1557,7 @@ static int ext4_ext_try_to_merge(struct
>               if (ext4_ext_is_uninitialized(ex))
>                       uninitialized = 1;
>               ex->ee_len = cpu_to_le16(ext4_ext_get_actual_len(ex)
> -                             + ext4_ext_get_actual_len(ex + 1));
> +                             + ext4_ext_get_actual_len(ex++));

After your change gcc complains:

 fs/ext4/extents.c:1559:16: warning: operation on ‘ex’ may be undefined
 fs/ext4/extents.c:1559:16: warning: operation on ‘ex’ may be undefined

which it is correct in doing since you are now modifying the value of the
pointer which is dereferenced in the assignment. Previously the value of
(ex+1) was simply passed to ext4_ext_get_actual_len(), but now you are
passing the value of (ex) to ext4_ext_get_actual_len() and then
subsequently incrementing 'ex' itself.


>               if (uninitialized)
>                       ext4_ext_mark_uninitialized(ex);
>
>


Was this patch even compile tested?


      

             reply	other threads:[~2010-11-04 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 23:34 André Luis Pereira dos Santos - BSRSoft [this message]
2010-11-05 12:52 ` Ted Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2010-11-04 22:07 André Luis Pereira dos Santos - BSRSoft
2010-11-04 22:31 ` Jesper Juhl
2010-11-04 22:44 ` Greg Freemyer

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=756314.4122.qm@web110514.mail.gq1.yahoo.com \
    --to=andre@bsrsoft.com.br \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®