From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 92D1BC7EE23 for ; Thu, 1 Jun 2023 17:43:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233037AbjFARns (ORCPT ); Thu, 1 Jun 2023 13:43:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38694 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231931AbjFARnq (ORCPT ); Thu, 1 Jun 2023 13:43:46 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C5CD51AD for ; Thu, 1 Jun 2023 10:43:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 5DA3364869 for ; Thu, 1 Jun 2023 17:43:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3FF30C433D2; Thu, 1 Jun 2023 17:43:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1685641416; bh=b2gcd3dJB++dyO99vAGT9rIkgCvbeypWxYxoChQXHXY=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=tqHvoIYQCtkmBJcXfzi5Bifu/Ja0qfXqNcCvM0UurkX11FYxuANVpQz/bs7T1oB17 y01rsU+dhuiDX460ANq1Mwmh9Jtm1Xo8RJEMZU5MU9n4gkpBz5ZoPaOGXimV0f3lOk 2YRv3JH82u+zAIVBOW38Ik7Wj3bitGiT0oNQBzUichFAqwwI9tC2nVr9LhCN04FhA5 4twBsPeiO9izaWy30sOF0LftUlI2ieaxfOPsk9v15dZTqxkWJVP9uzrVvcebzPd4r3 NQzKJN9S883XO5iYq67+vbhfiHkDznmchHEwQ65cv65U705bdZroVMqDrPp7Gs6EkA voErZ5DxEPriw== Message-ID: <63ee166d-6b33-2293-4ff2-2c42d350580a@kernel.org> Date: Thu, 1 Jun 2023 11:43:35 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: [PATCH net-next RFC] net: skip printing "link become ready" v6 msg Content-Language: en-US To: Stephen Hemminger , Matthieu Baerts Cc: mptcp@lists.linux.dev, "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Mat Martineau , Hideaki YOSHIFUJI , netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230601-net-next-skip_print_link_becomes_ready-v1-1-c13e64c14095@tessares.net> <20230601103742.71285cf1@hermes.local> From: David Ahern In-Reply-To: <20230601103742.71285cf1@hermes.local> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/1/23 11:37 AM, Stephen Hemminger wrote: > On Thu, 01 Jun 2023 16:34:36 +0200 > Matthieu Baerts wrote: > >> This following message is printed in the console each time a network >> device configured with an IPv6 addresses is ready to be used: >> >> ADDRCONF(NETDEV_CHANGE): : link becomes ready >> >> When netns are being extensively used -- e.g. by re-creating netns with >> veth to discuss with each other for testing purposes like mptcp_join.sh >> selftest does -- it generates a lot of messages: more than 700 when >> executing mptcp_join.sh with the latest version. > > Don't add yet another network nerd knob. > Just change message from pr_info to pr_debug. +1