From: Theodore Tso <tytso@mit.edu>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
sct@redhat.com, adilger@sun.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ext3, ext4: make i signed in do_split()
Date: Fri, 5 Dec 2008 11:32:01 -0500 [thread overview]
Message-ID: <20081205163201.GG1323@mit.edu> (raw)
In-Reply-To: <4935A21A.60509@gmail.com>
On Tue, Dec 02, 2008 at 10:01:14PM +0100, Roel Kluin wrote:
> Andrew Morton wrote:
> > On Sat, 29 Nov 2008 04:40:42 -0500
> > roel kluin <roel.kluin@gmail.com> wrote:
> >
> >> unsigned i >= 0 is always true
>
> >> - for (i = count-1; i >= 0; i--) {
> >> + for (i = count-1; i < count; i--) {
> break;
>
> > A local variable called `i' should always have signed type. In fact,
> > it should have `int' type.
>
> You are right. although count is unsigned, dx_make_map() returns int, which is
> assigned to count, so this should fit in an int. (If you ack this, make sure to
> get this patch, and not one of the others.)
ACK. I'll take care of getting this into the patch queue. I'll
include both the ext3 and ext4 variants, since this one is simple
enough that it's highly unlikely to conflict with anything Andrew
might have in the -mm tree. This is also much more of a cleanup than
anything else, so I don't think we need to push it until the merge
window. (I *think* it might be possible for a 2k filesystems and
*very* long filenames we might possibly be able to trigger a
failure but it would be very hard to do, and it's been around for a
very long time without anyone complaining about an actual real-life
problem getting trigger.)
- Ted
prev parent reply other threads:[~2008-12-05 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 9:40 [PATCH] ext3: also fix loop in do_split() roel kluin
2008-12-02 20:07 ` Andrew Morton
2008-12-02 20:29 ` Eric Sandeen
2008-12-02 21:01 ` [PATCH v4] ext3, ext4: make i signed " Roel Kluin
2008-12-05 16:32 ` Theodore Tso [this message]
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=20081205163201.GG1323@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=sct@redhat.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).