From: Thaison Phan <thaisonphan@google.com>
To: kuba@kernel.org
Cc: davem@davemloft.net, edumazet@google.com, gfengyuan@google.com,
horms@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, petrm@nvidia.com, shuah@kernel.org,
stani@google.com, thaisonphan@google.com, willemb@google.com
Subject: Re: [PATCH net-next] selftests: net: update wait mechanism for relocating
Date: Wed, 22 Jul 2026 16:21:35 +0000 [thread overview]
Message-ID: <20260722162135.331826-1-thaisonphan@google.com> (raw)
In-Reply-To: <20260721115339.09a3ea0e@kernel.org>
> I don't get it. I never saw it hang. And if the event is scoped udevadm settle
> should return immediately, rather than hang. We generally run on latest
> systemd udev in Fedora and CentOS. Please explain your problem better.
Thanks for reviewing this. I looked into my issue further. I found out when I
run into the hanging problem, the machine that I run on is using an internal
Linux distro that turns out to be running an old version (182) of udev before it
was merged to be a part of systemd. The source code for udev I was referencing
was out of date where it looks like udevadm settle relied on an internal uevent
sequence number to match up with a kernel uevent sequence number. At some point
I think it was a known problem that these sequence numbers could become out of
sync because udev would never get uevents not tied to the default namespace. I
checked the upstream udev and saw that udevadm settle was refactored, so that
sequence numbers are now deprecated. This patch is only applicable for versions of
udev without the refactor, so there is probably no reason to upstream it.
> Should be a separate patch
Sounds good. I'll create a separate patch for the exception fix.
prev parent reply other threads:[~2026-07-22 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 16:08 [PATCH net-next] selftests: net: update wait mechanism for relocating netdevsim to a new ns Thaison Phan
2026-07-21 18:53 ` Jakub Kicinski
2026-07-22 16:21 ` Thaison Phan [this message]
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=20260722162135.331826-1-thaisonphan@google.com \
--to=thaisonphan@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gfengyuan@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--cc=stani@google.com \
--cc=willemb@google.com \
/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®