Am 08.04.2013 22:20, schrieb John Stultz:
On 03/19/2013 05:29 AM, David Engraf wrote:
Hello,
I've triggered an overflow when using ktime_add_ns() on a 32bit
architecture not supporting CONFIG_KTIME_SCALAR.
When passing a very high value for u64 nsec, e.g. 7881299347898368000
the do_div() funct
On 03/19/2013 05:29 AM, David Engraf wrote:
Hello,
I've triggered an overflow when using ktime_add_ns() on a 32bit
architecture not supporting CONFIG_KTIME_SCALAR.
When passing a very high value for u64 nsec, e.g. 7881299347898368000
the do_div() function converts this value to seconds (7881
Am 19.03.2013 13:38, schrieb Eric Dumazet:
On Tue, 2013-03-19 at 13:29 +0100, David Engraf wrote:
Hello,
I've triggered an overflow when using ktime_add_ns() on a 32bit
architecture not supporting CONFIG_KTIME_SCALAR.
When passing a very high value for u64 nsec, e.g. 7881299347898368000
the do
On Tue, 2013-03-19 at 13:29 +0100, David Engraf wrote:
> Hello,
>
> I've triggered an overflow when using ktime_add_ns() on a 32bit
> architecture not supporting CONFIG_KTIME_SCALAR.
>
> When passing a very high value for u64 nsec, e.g. 7881299347898368000
> the do_div() function converts this
Hello,
I've triggered an overflow when using ktime_add_ns() on a 32bit
architecture not supporting CONFIG_KTIME_SCALAR.
When passing a very high value for u64 nsec, e.g. 7881299347898368000
the do_div() function converts this value to seconds (7881299347) which
is still to high to pass to th
5 matches
Mail list logo