size_t-to-int vulnerability in Linux’s filesystem layer

Re:size_t-to-int vulnerability in Linux’s filesystem layer by tialaramex on Tuesday July 20, 2021 @01:54PM (#27896952)

Linux apparently provides a similarly named set of sized integer types to Rust, ie: s8 u8 s16 u16 s32 u32 s64 u64

But of course getting C programmers to use these integer types rather than the ones they grew up with isn't easy.

[ Parent | on HN ]

Re:size_t-to-int vulnerability in Linux’s filesystem layer by foobiekr on Tuesday July 20, 2021 @03:31PM (#27898165)

I did a lot of C - a lot - in the mid-90s through the mid/late 2000s and have never seen any sizable C code base where explicit sizes were not the norm throughout - u_int32_t etc. I think this is not the problem, it's the implicit conversions.

[ Parent | on HN ]

Re:size_t-to-int vulnerability in Linux’s filesystem layer by masklinn on Wednesday July 21, 2021 @03:46AM (#27903479)

I don't think that stops C's implicit conversions either, does it?

[ Parent | on HN ]

Re:size_t-to-int vulnerability in Linux’s filesystem layer by dezgeg on Wednesday July 21, 2021 @10:37AM (#27906865)

It doesn't. They are in the end just typedefs to the basic types like int, long, etc.

[ Parent | on HN ]