Searched hist:"8253947 e2cdfb14717c9212b751b7aec9ea9ef5e" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/net/core/ |
| H A D | rtnetlink.c | diff 8253947e2cdfb14717c9212b751b7aec9ea9ef5e Sun Jul 29 11:01:30 CDT 2012 Li Wei <lw@cn.fujitsu.com> ipv6: fix incorrect route 'expires' value passed to userspace
When userspace use RTM_GETROUTE to dump route table, with an already
expired route entry, we always got an 'expires' value(2147157)
calculated base on INT_MAX.
The reason of this problem is in the following satement:
rt->dst.expires - jiffies < INT_MAX
gcc promoted the type of both sides of '<' to unsigned long, thus
a small negative value would be considered greater than INT_MAX.
With the help of Eric Dumazet, do the out of bound checks in
rtnl_put_cacheinfo(), _after_ conversion to clock_t.
Signed-off-by: Li Wei <lw@cn.fujitsu.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/ipv6/ |
| H A D | route.c | diff 8253947e2cdfb14717c9212b751b7aec9ea9ef5e Sun Jul 29 11:01:30 CDT 2012 Li Wei <lw@cn.fujitsu.com> ipv6: fix incorrect route 'expires' value passed to userspace
When userspace use RTM_GETROUTE to dump route table, with an already
expired route entry, we always got an 'expires' value(2147157)
calculated base on INT_MAX.
The reason of this problem is in the following satement:
rt->dst.expires - jiffies < INT_MAX
gcc promoted the type of both sides of '<' to unsigned long, thus
a small negative value would be considered greater than INT_MAX.
With the help of Eric Dumazet, do the out of bound checks in
rtnl_put_cacheinfo(), _after_ conversion to clock_t.
Signed-off-by: Li Wei <lw@cn.fujitsu.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|