mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Haller <thaller@redhat.com>
To: Lubomir Rintel <lkundrak@v3.sk>,
	"David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/ipv6: lower the level of "link is not ready" messages
Date: Mon, 21 Jan 2019 16:52:04 +0100	[thread overview]
Message-ID: <47c97a0e4fc1a520d166b69d4ca19e36049f8eba.camel@redhat.com> (raw)
In-Reply-To: <20190121135419.615989-1-lkundrak@v3.sk>

On Mon, 2019-01-21 at 14:54 +0100, Lubomir Rintel wrote:
> This message gets logged far too often for how interesting is it.
> 
> Most distributions nowadays configure NetworkManager to use randomly
> generated MAC addresses for Wi-Fi network scans. The interfaces end
> up
> being periodically brought down for the address change. When they're
> subsequently brought back up, the message is logged, eventually
> flooding
> the log.
> 
> Perhaps the message is not all that helpful: it seems to be more
> interesting to hear when the addrconf actually start, not when it
> does
> not. Let's lower its level.
> 
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>


Hi,

a NetworkManager maintainer here.

Acked-By: Thomas Haller <thaller@redhat.com>


> ---
>  net/ipv6/addrconf.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
> index 93d5ad2b1a69..ba155841dc15 100644
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@ -3495,8 +3495,8 @@ static int addrconf_notify(struct
> notifier_block *this, unsigned long event,
>  
>  			if (!addrconf_link_ready(dev)) {
>  				/* device is not ready yet. */
> -				pr_info("ADDRCONF(NETDEV_UP): %s: link
> is not ready\n",
> -					dev->name);
> +				pr_debug("ADDRCONF(NETDEV_UP): %s: link
> is not ready\n",
> +					 dev->name);
>  				break;
>  			}





  reply	other threads:[~2019-01-21 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 13:54 Lubomir Rintel
2019-01-21 15:52 ` Thomas Haller [this message]
2019-01-23  4:43 ` 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=47c97a0e4fc1a520d166b69d4ca19e36049f8eba.camel@redhat.com \
    --to=thaller@redhat.com \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --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

all inboxes | Powered by JetHome®