netdev_unregister_timeout_secs=0 can lead to printing the
"waiting for dev to become free" message every jiffy.
This is too frequent and unnecessary.
Set the min value to 1 second.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Suggested-by: Eric Dumazet <edumazet@google.com>
Fixes: 5aa3afe107d9 ("net: make unregister netdev warning timeout configurable")
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Documentation/admin-guide/sysctl/net.rst | 2 +-
net/core/sysctl_net_core.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
@@ -320,7 +320,7 @@ waiting for a network device refcount to drop to 0 during device unregistration. A lower value may be useful during bisection to detect a leaked reference faster. A larger value may be useful to prevent false warnings on slow/loaded systems.-Default value is 10, minimum 0, maximum 3600.+Default value is 10, minimum 1, maximum 3600. optmem_max ----------
From: Eric Dumazet <hidden> Date: 2021-03-25 14:35:36
On 3/25/21 11:31 AM, Dmitry Vyukov wrote:
netdev_unregister_timeout_secs=0 can lead to printing the
"waiting for dev to become free" message every jiffy.
This is too frequent and unnecessary.
Set the min value to 1 second.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Suggested-by: Eric Dumazet <edumazet@google.com>
Fixes: 5aa3afe107d9 ("net: make unregister netdev warning timeout configurable")
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Please respin your patch, and fix the merge issue [1]
For networking patches it is customary to tell if its for net or net-next tree.
[1]
On Thu, Mar 25, 2021 at 3:34 PM Eric Dumazet [off-list ref] wrote:
On 3/25/21 11:31 AM, Dmitry Vyukov wrote:
quoted
netdev_unregister_timeout_secs=0 can lead to printing the
"waiting for dev to become free" message every jiffy.
This is too frequent and unnecessary.
Set the min value to 1 second.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Suggested-by: Eric Dumazet <edumazet@google.com>
Fixes: 5aa3afe107d9 ("net: make unregister netdev warning timeout configurable")
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Please respin your patch, and fix the merge issue [1]
Is net-next rebuilt and rebased? Do I send v4 of the whole change?
I cannot base it on net-next now, because net-next already includes
most of it... so what should I use as base then?
quoted hunk
For networking patches it is customary to tell if its for net or net-next tree.
[1]
From: Eric Dumazet <hidden> Date: 2021-03-25 14:44:43
On 3/25/21 3:38 PM, Dmitry Vyukov wrote:
On Thu, Mar 25, 2021 at 3:34 PM Eric Dumazet [off-list ref] wrote:
quoted
On 3/25/21 11:31 AM, Dmitry Vyukov wrote:
quoted
netdev_unregister_timeout_secs=0 can lead to printing the
"waiting for dev to become free" message every jiffy.
This is too frequent and unnecessary.
Set the min value to 1 second.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Suggested-by: Eric Dumazet <edumazet@google.com>
Fixes: 5aa3afe107d9 ("net: make unregister netdev warning timeout configurable")
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Please respin your patch, and fix the merge issue [1]
Is net-next rebuilt and rebased? Do I send v4 of the whole change?
I cannot base it on net-next now, because net-next already includes
most of it... so what should I use as base then?
quoted
For networking patches it is customary to tell if its for net or net-next tree.
[1]
@@ -10431,7 +10431,7 @@ static void netdev_wait_allrefs(struct net_device *dev)refcnt=netdev_refcnt_read(dev);-if(refcnt&&+if(refcnt!=1&&time_after(jiffies,warning_time+netdev_unregister_timeout_secs*HZ)){pr_emerg("unregister_netdevice: waiting for %s to become free. Usage count = %d\n",
Please include my fix into your patch.
Send a V2, based on current net-next.
net-next is never rebased, we have to fix the bug by adding a fix on top of it.
On Thu, Mar 25, 2021 at 3:43 PM Eric Dumazet [off-list ref] wrote:
On 3/25/21 3:38 PM, Dmitry Vyukov wrote:
quoted
On Thu, Mar 25, 2021 at 3:34 PM Eric Dumazet [off-list ref] wrote:
quoted
On 3/25/21 11:31 AM, Dmitry Vyukov wrote:
quoted
netdev_unregister_timeout_secs=0 can lead to printing the
"waiting for dev to become free" message every jiffy.
This is too frequent and unnecessary.
Set the min value to 1 second.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Suggested-by: Eric Dumazet <edumazet@google.com>
Fixes: 5aa3afe107d9 ("net: make unregister netdev warning timeout configurable")
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Please respin your patch, and fix the merge issue [1]
Is net-next rebuilt and rebased? Do I send v4 of the whole change?
I cannot base it on net-next now, because net-next already includes
most of it... so what should I use as base then?
quoted
For networking patches it is customary to tell if its for net or net-next tree.
[1]
@@ -10431,7 +10431,7 @@ static void netdev_wait_allrefs(struct net_device *dev)refcnt=netdev_refcnt_read(dev);-if(refcnt&&+if(refcnt!=1&&time_after(jiffies,warning_time+netdev_unregister_timeout_secs*HZ)){pr_emerg("unregister_netdevice: waiting for %s to become free. Usage count = %d\n",
Please include my fix into your patch.
Send a V2, based on current net-next.
net-next is never rebased, we have to fix the bug by adding a fix on top of it.
Ah, got it. Mailed:
[PATCH net-next v2] net: change netdev_unregister_timeout_secs min value to 1