From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Steven French <sfrench@us.ibm.com>
Cc: acc@CS.Stanford.EDU, linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] 16 more potential buffer overruns in 2.5.48
Date: Wed, 20 Nov 2002 12:11:12 -0500 [thread overview]
Message-ID: <3DDBC230.6000908@nortelnetworks.com> (raw)
In-Reply-To: OFF1AA16C4.904AD55A-ON87256C77.00529B26@us.ibm.com
Steven French wrote:
> As long as unsigned char can never go above 255 the code should
> work. It might have be more readable if it were defined as a __u8
> instead of an unsigned char.
Technically there is nothing that guarantees that an unsigned char is <=
8 bytes in size (although in practice it often is the case).
__u8 would definately be the way to go.
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-11-20 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 16:56 [CHECKER] 16 more potential buffer overruns in 2.5.48 Steven French
2002-11-20 17:05 ` Jeff Garzik
2002-11-20 17:11 ` Chris Friesen [this message]
2002-11-20 18:02 ` Mark Mielke
-- strict thread matches above, loose matches on Subject: below --
2002-11-20 8:49 Andy Chou
2002-11-30 23:51 ` Jeff Garzik
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=3DDBC230.6000908@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=acc@CS.Stanford.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.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 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.