From: Leon Romanovsky <leon@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: davem@davemloft.net, edumazet@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: make unregister netdev warning timeout configurable
Date: Wed, 24 Mar 2021 11:32:03 +0200 [thread overview]
Message-ID: <YFsHEwkqCq91ngwn@unreal> (raw)
In-Reply-To: <20210323064923.2098711-1-dvyukov@google.com>
On Tue, Mar 23, 2021 at 07:49:23AM +0100, Dmitry Vyukov wrote:
> netdev_wait_allrefs() issues a warning if refcount does not drop to 0
> after 10 seconds. While 10 second wait generally should not happen
> under normal workload in normal environment, it seems to fire falsely
> very often during fuzzing and/or in qemu emulation (~10x slower).
> At least it's not possible to understand if it's really a false
> positive or not. Automated testing generally bumps all timeouts
> to very high values to avoid flake failures.
> Add net.core.netdev_unregister_timeout_secs sysctl to make
> the timeout configurable for automated testing systems.
> Lowering the timeout may also be useful for e.g. manual bisection.
> The default value matches the current behavior.
>
> Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
> Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=211877
> Cc: netdev@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
> ---
> Changes since v1:
> - use sysctl instead of a config
> ---
> Documentation/admin-guide/sysctl/net.rst | 11 +++++++++++
> include/linux/netdevice.h | 1 +
> net/core/dev.c | 6 +++++-
> net/core/sysctl_net_core.c | 10 ++++++++++
> 4 files changed, 27 insertions(+), 1 deletion(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2021-03-24 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 6:49 [PATCH v2] net: make unregister netdev warning timeout configurable Dmitry Vyukov
2021-03-24 9:32 ` Leon Romanovsky [this message]
2021-03-24 9:40 ` Eric Dumazet
2021-03-25 7:39 ` Dmitry Vyukov
2021-03-25 8:46 ` Eric Dumazet
2021-03-25 10:32 ` Dmitry Vyukov
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=YFsHEwkqCq91ngwn@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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