Re: [patch net-next v3] ipv6: log autoconfiguration failures

2013-12-14 Thread Hannes Frederic Sowa
On Fri, Dec 13, 2013 at 05:57:09PM -0500, David Miller wrote: > From: Denys Vlasenko > Date: Fri, 13 Dec 2013 16:45:47 +0100 > > > If ipv6 auto-configuration does not work, currently it's hard > > to track what's going on. This change adds log messages > > (at debug level) on every code path wher

Re: [patch net-next v3] ipv6: log autoconfiguration failures

2013-12-13 Thread David Miller
From: Denys Vlasenko Date: Fri, 13 Dec 2013 16:45:47 +0100 > If ipv6 auto-configuration does not work, currently it's hard > to track what's going on. This change adds log messages > (at debug level) on every code path where ipv6 autoconf fails. > > v3: changed pr_debug's to pr_warn's. > > Sign

Re: [patch net-next v3] ipv6: log autoconfiguration failures

2013-12-13 Thread Vlad Yasevich
On 12/13/2013 10:45 AM, Denys Vlasenko wrote: > If ipv6 auto-configuration does not work, currently it's hard > to track what's going on. This change adds log messages > (at debug level) on every code path where ipv6 autoconf fails. > > v3: changed pr_debug's to pr_warn's. > > Signed-off-by: Deny

[patch net-next v3] ipv6: log autoconfiguration failures

2013-12-13 Thread Denys Vlasenko
If ipv6 auto-configuration does not work, currently it's hard to track what's going on. This change adds log messages (at debug level) on every code path where ipv6 autoconf fails. v3: changed pr_debug's to pr_warn's. Signed-off-by: Denys Vlasenko --- net/ipv6/addrconf.c | 45 ++