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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Dec 2013 12:17:42 +0100
From:	Denys Vlasenko <dvlasenk@...hat.com>
To:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	davem@...emloft.net, Alexey Kuznetsov <kuznet@....inr.ac.ru>,
	James Morris <jmorris@...ei.org>,
	Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
	Patrick McHardy <kaber@...sh.net>, jpirko@...hat.com
Subject: Re: [patch net-next v2] ipv6: log autoconfiguration failures

On 12/11/2013 08:21 PM, Hannes Frederic Sowa wrote:
> On Wed, Dec 11, 2013 at 12:45:14PM +0100, 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.
>>
>> v2: fixed indentation in multi-line log output statements.
> 
> Have you seen lots of those problems? Some of those seem like very
> serious problems and maybe could also deserve a pr_warn or pr_err.

I personally wasn't bitten by this problem, but our admins were.

They say that when they notice that ipv6 auconf didn't work
(i.e. they see no auconfigured addresses on the interfaces),
they usually see no useful messages in dmesg or /var/log/messages,
which makes them to try to fix the problem blind.

I can easily imagine their frustration. Kernel _knows_ why
it didn't work, and it's not expected to normally pappen,
why didn't it tell anything about it?

-- 
vda


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html