netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dvlasenk@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	kaber@trash.net, jpirko@redhat.com
Subject: Re: [patch net-next v2] ipv6: log autoconfiguration failures
Date: Thu, 12 Dec 2013 12:22:41 -0500 (EST)	[thread overview]
Message-ID: <20131212.122241.2022824170198915190.davem@davemloft.net> (raw)
In-Reply-To: <52A99B56.1070503@redhat.com>

From: Denys Vlasenko <dvlasenk@redhat.com>
Date: Thu, 12 Dec 2013 12:17:42 +0100

> 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?

Packets are dropped silently, ARP fails and entries go stale silently,
none of this is logged with kernel messages, why is ipv6 autoconf so
unique and important to justify different behavior?

Give it statistics just like we have for every other kind of similar
event.

  reply	other threads:[~2013-12-12 17:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 11:45 [patch net-next v2] ipv6: log autoconfiguration failures Denys Vlasenko
2013-12-11 19:21 ` Hannes Frederic Sowa
2013-12-11 20:54   ` David Miller
2013-12-11 21:09     ` Hannes Frederic Sowa
2013-12-12 11:28     ` Denys Vlasenko
2013-12-12 17:24       ` David Miller
2013-12-12 11:17   ` Denys Vlasenko
2013-12-12 17:22     ` David Miller [this message]
2013-12-12 17:58       ` Vlad Yasevich
2013-12-12 18:24         ` David Miller
2013-12-12 19:00           ` Hannes Frederic Sowa
2013-12-12 19:06             ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131212.122241.2022824170198915190.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dvlasenk@redhat.com \
    --cc=jmorris@namei.org \
    --cc=jpirko@redhat.com \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).