David Howells writes:
> Mitsuo Hayasaka wrote:
>
>> When we read the sysctl parameter, they are always treated
>> as signed integer, and are casted into unsigned long type
>> in the current kernel. If we set a value equivalent to
>> (the maximum value in signed integer + 1)
>
> Wouldn't it be
Mitsuo Hayasaka wrote:
> When we read the sysctl parameter, they are always treated
> as signed integer, and are casted into unsigned long type
> in the current kernel. If we set a value equivalent to
> (the maximum value in signed integer + 1)
Wouldn't it be better to return EINVAL or EDOM?
Hi,
This patch fixes the improper type casting of integer
sysctl parameters.
When we read the sysctl parameter, they are always treated
as signed integer, and are casted into unsigned long type
in the current kernel. If we set a value equivalent to
(the maximum value in signed integer + 1) which
Hi,
This patch fixes the improper type casting of integer
sysctl parameters.
When we read the sysctl parameter, they are always treated
as signed integer, and are casted into unsigned long type
in the current kernel. If we set a value equivalent to
(the maximum value in signed integer + 1) which
Mitsuo Hayasaka mitsuo.hayasaka...@hitachi.com wrote:
When we read the sysctl parameter, they are always treated
as signed integer, and are casted into unsigned long type
in the current kernel. If we set a value equivalent to
(the maximum value in signed integer + 1)
Wouldn't it be better to
David Howells dhowe...@redhat.com writes:
Mitsuo Hayasaka mitsuo.hayasaka...@hitachi.com wrote:
When we read the sysctl parameter, they are always treated
as signed integer, and are casted into unsigned long type
in the current kernel. If we set a value equivalent to
(the maximum value in
6 matches
Mail list logo
