Re: [PATCH 1/2] ipv6: Clamp reported valid_lft to a minimum of 0

[PATCH 1/2] ipv6: Clamp reported valid_lft to a minimum of 0 · Ben Hutchings <hidden> · 2010-06-26
[PATCH 2/2] ipv6: Use interface max_desync_factor instead of static default · Ben Hutchings <hidden> · 2010-06-26
Re: [PATCH 2/2] ipv6: Use interface max_desync_factor instead of static default · David Miller <davem@davemloft.net> · 2010-06-30
Re: [PATCH 1/2] ipv6: Clamp reported valid_lft to a minimum of 0 · David Miller <davem@davemloft.net> · 2010-06-30

From: David Miller <davem@davemloft.net>
Date: 2010-06-30 17:28:42

From: Ben Hutchings <redacted>
Date: Sat, 26 Jun 2010 22:37:47 +0100

Since addresses are only revalidated every 2 minutes, the reported
valid_lft can underflow shortly before the address is deleted.
Clamp it to a minimum of 0, as for prefered_lft.

Reported-by: Piotr Lewandowski <redacted>
Signed-off-by: Ben Hutchings <redacted>

Applied to net-next-2.6

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help