Thread (22 messages) flat view 22 messages, 5 authors, 2026-02-21

Re: [PATCH net v2 4/4] selftests: drv-net: rss_ctx: test RSS contexts persist after ifdown/up

From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-02-11 16:31:34

On Wed, 11 Feb 2026 13:29:06 +0530 Pavan Chebbi wrote:
quoted
quoted
If you check the carrier manually in a second terminal while it's
running -- do you see it go to 1? The helper keeps the file open  
Thanks for the nudge. I think I get the real issue now. It's not the
cmd() but ifup.exec()
I am using :
ifup = defer(ip, f"link set dev {cfg.ifname} up")
and later
ifup.exec()

I see that exec() takes unusually long time for carrier to go to 1.
Upto 20s and sometimes still fails.
Same with both direct exec or deferred. And this explains why I cannot
ping for long time after suite exists. Thats because I rely on defer()
to bring the interface up after bnxt exits with carrier 0 for the
second test.
If replace the exec with direct call to ip(f"link set dev {cfg.ifname}
up") I see it works reliably.
My experiments are pointing to 'self.cancel()' sometimes taking a lot
of time as part of the exec().
I don't know but I feel the new test code itself should be OK. I can
send a v3 and you can run it once too?
Could you reply to this thread with what the version of the patch where
you see defer() takes a long time? We use defer all over the place..
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help