From: XIAO Gang <xiao@unice.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Suggestion on "int len" sanity
Date: Thu, 02 Jun 2005 09:28:55 +0200 [thread overview]
Message-ID: <429EB537.4060305@unice.fr> (raw)
Willy Tarreau wrote:
>> On the other hand, when a variable is named "len" or "length", it is
>> usually used for length and never should go negative. So could I suggest
>> that the declarations of these variables to be uniformized to "size_t",
>> via a gradual but sysmatic cleanup?
> Probably true for most cases, but be careful of code which would use
> -1 to report some errors if such thing exists.
I agree that they are probably not all replaceable, and care must be taken.
Examples:
1. In the types of sys_[gs]ethostname, sys_[gs]etdomainname, "int len" could be replaced
by "unsigned int" or "size_t" and sanity check simplified.
2. In mm/shmem.c, shmem_symlink(), we have "len = strlen(symname) + 1;". Although it is highly
improbable that strlen(symname) overflows, it is more correct to declare "size_t len;".
3. The similar situation occurs in fs/namei.c, vfs_readlink(). Here it does not matter if len
is declared to be unsigned, but for size_t, we have to take care about the size of size_t.
--
XIAO Gang (~{P$8U~}) xiao@unice.fr
home page: pcmath126.unice.fr/xiao.html
next reply other threads:[~2005-06-02 7:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 7:28 XIAO Gang [this message]
2005-06-02 8:48 ` Jörn Engel
2005-06-02 9:12 ` XIAO Gang
2005-06-02 9:47 ` Jörn Engel
2005-06-03 9:45 ` Geert Uytterhoeven
2005-06-03 12:20 ` Al Viro
2005-06-03 14:19 ` Jörn Engel
2005-06-03 12:28 ` Andreas Schwab
2005-06-03 12:43 ` Geert Uytterhoeven
2005-06-03 14:38 ` Andreas Schwab
2005-06-03 18:04 ` randy_dunlap
2005-06-03 18:09 ` Lars Marowsky-Bree
2005-06-03 18:16 ` randy_dunlap
2005-06-04 11:28 ` Christoph Hellwig
2005-06-04 16:58 ` randy_dunlap
2005-06-04 17:07 ` Jörn Engel
2005-06-04 17:11 ` randy_dunlap
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 7:06 XIAO Gang
2005-06-01 13:46 ` Jörn Engel
2005-06-01 20:39 ` Willy Tarreau
2005-06-03 9:42 ` Geert Uytterhoeven
2005-06-03 12:47 ` Takashi Iwai
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=429EB537.4060305@unice.fr \
--to=xiao@unice.fr \
--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
Powered by JetHome