From: Bill Davidsen <davidsen@tmr.com>
To: roel kluin <roel.kluin@gmail.com>
Cc: tytso@mit.edu, adilger@sun.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: fix loop in do_split()
Date: Sat, 29 Nov 2008 19:36:52 -0500 [thread overview]
Message-ID: <4931E024.2010500@tmr.com> (raw)
In-Reply-To: <49310D34.1000205@gmail.com>
roel kluin wrote:
> unsigned i >= 0 is always true
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> index 63adcb7..389cf60 100644
> --- a/fs/ext4/namei.c
> +++ b/fs/ext4/namei.c
> @@ -1198,7 +1198,7 @@ static struct ext4_dir_entry_2 *do_split(handle_t *handle, struct inode *dir,
> /* Split the existing block in the middle, size-wise */
> size = 0;
> move = 0;
> - for (i = count-1; i >= 0; i--) {
> + for (i = count-1; i < count; i--) {
> /* is more than half of this entry in 2nd half of the block? */
> if (size + map[i].size/2 > blocksize/2)
> break;
>
While this unsigned wrap method is technically valid, it certainly isn't
obvious, and making code readable should be a goal as well as making it correct.
After all, code which is hard to read is hard to understand, making it hard to
maintain. I therefore suggest the simpler form:
for (i = count; i--; ) {
which gives the same i values inside the loop, but does assume that the reader
remembers that i is unsigned, and intuitively understand wraparound while
passing zero.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
WARNING: multiple messages have this Message-ID (diff)
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: fix loop in do_split()
Date: Sat, 29 Nov 2008 19:36:52 -0500 [thread overview]
Message-ID: <4931E024.2010500@tmr.com> (raw)
In-Reply-To: <49310D34.1000205@gmail.com>
roel kluin wrote:
> unsigned i >= 0 is always true
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> index 63adcb7..389cf60 100644
> --- a/fs/ext4/namei.c
> +++ b/fs/ext4/namei.c
> @@ -1198,7 +1198,7 @@ static struct ext4_dir_entry_2 *do_split(handle_t *handle, struct inode *dir,
> /* Split the existing block in the middle, size-wise */
> size = 0;
> move = 0;
> - for (i = count-1; i >= 0; i--) {
> + for (i = count-1; i < count; i--) {
> /* is more than half of this entry in 2nd half of the block? */
> if (size + map[i].size/2 > blocksize/2)
> break;
>
While this unsigned wrap method is technically valid, it certainly isn't
obvious, and making code readable should be a goal as well as making it correct.
After all, code which is hard to read is hard to understand, making it hard to
maintain. I therefore suggest the simpler form:
for (i = count; i--; ) {
which gives the same i values inside the loop, but does assume that the reader
remembers that i is unsigned, and intuitively understand wraparound while
passing zero.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-11-30 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 9:36 [PATCH] ext4: fix loop in do_split() roel kluin
2008-11-30 0:36 ` Bill Davidsen [this message]
2008-11-30 0:36 ` Bill Davidsen
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=4931E024.2010500@tmr.com \
--to=davidsen@tmr.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.