Bug#514646: [PATCH 2/2] ipv6: Use interface max_desync_factor instead of static default

To: ben@decadent.org.uk
Cc: yoshfuji@linux-ipv6.org, kaber@trash.net, 514646@bugs.debian.org, piotr.lewandowski@gmail.com, netdev@vger.kernel.org
Subject: Bug#514646: [PATCH 2/2] ipv6: Use interface max_desync_factor instead of static default
From: David Miller <davem@davemloft.net>
Date: Wed, 30 Jun 2010 10:29:02 -0700 (PDT)
Message-id: <20100630.102902.148553067.davem@davemloft.net>
Reply-to: David Miller <davem@davemloft.net>, 514646@bugs.debian.org
In-reply-to: <1277588575.26161.311.camel@localhost>
References: <1277588267.26161.300.camel@localhost> <1277588575.26161.311.camel@localhost>

From: Ben Hutchings <ben@decadent.org.uk>
Date: Sat, 26 Jun 2010 22:42:55 +0100

> max_desync_factor can be configured per-interface, but nothing is
> using the value.
> 
> Reported-by: Piotr Lewandowski <piotr.lewandowski@gmail.com>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>

Applied to net-next-2.6

Reply to:

References:
- Bug#514644: [PATCH 1/2] ipv6: Clamp reported valid_lft to a minimum of 0
  - From: Ben Hutchings <ben@decadent.org.uk>
- Bug#514646: [PATCH 2/2] ipv6: Use interface max_desync_factor instead of static default
  - From: Ben Hutchings <ben@decadent.org.uk>

Prev by Date: Bug#514644: [PATCH 1/2] ipv6: Clamp reported valid_lft to a minimum of 0
Next by Date: Bug#586558: [stable] [PATCH] Btrfs: should add a permission check for setfacl
Previous by thread: Bug#514646: [PATCH 2/2] ipv6: Use interface max_desync_factor instead of static default
Next by thread: Bug#514644: [PATCH 1/2] ipv6: Clamp reported valid_lft to a minimum of 0
Index(es):
- Date
- Thread