Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1500612
| From | none <ytrezq@sdf-eu.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | when to size_t for representing length instead of int ? |
| Date | 2016-10-14 00:30 +0200 |
| Message-ID | <srWFH-180-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Hello, I wanted to known the rules in coding guidelines concerning the use of size_t. It seems the signed int type is used most of the time for representing string sizes, including in some parts written by Linus in /lib. They’re can buffer overflows attack if ssize_t if larger than sizeof(int) (though I agree this isn’t the only way, but at least it´s less error prone). So is it guaranteed for all current and future cpu architectures the Linux kernel support that ssize_t will always be equal to sizeof(int) ? regards,
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
when to size_t for representing length instead of int ? none <ytrezq@sdf-eu.org> - 2016-10-14 00:30 +0200
Re: when to size_t for representing length instead of int ? Al Viro <viro@ZenIV.linux.org.uk> - 2016-10-14 01:40 +0200
Re: when to size_t for representing length instead of int ? none <ytrezq@sdf-eu.org> - 2016-10-16 04:10 +0200
csiph-web