From: netdev-bot+sashiko@kernel.org
To: almasrymina@google.com
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, pabeni@redhat.com,
sdf@fomichev.me, kaiyuanz@google.com, kuba@kernel.org,
bobbyeshleman@meta.com, asml.silence@gmail.com, dw@davidwei.uk,
ap420073@gmail.com, davem@davemloft.net, edumazet@kernel.org,
horms@kernel.org, shuah@kernel.org, sumit.semwal@linaro.org,
christian.koenig@amd.com, phasta@kernel.org,
andrew+netdev@lunn.ch, sdf.kernel@gmail.com, hawk@kernel.org,
ilias.apalodimas@linaro.org, daniel@iogearbox.net,
razor@blackwall.org, tariqt@nvidia.com, kaifengw@google.com,
dtatulea@nvidia.com
Subject: Re: [PATCH net v5 4/4] selftests: net: add devmem RX and TX netdev unregister tests
Date: Sun, 01 Nov 2026 23:01:27 +0000 [thread overview]
Message-ID: <179357408797.3131.706180156061595645@kernel.org> (raw)
In-Reply-To: <20261030083539.777877-5-almasrymina@google.com>
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] The patch adds CONFIG_UDMABUF=y to
tools/testing/selftests/net/config, but the fragment does not pull in…
--
selftests: net: add devmem RX and TX netdev unregister tests
This adds devmem_bind_rx_unregister_check and
devmem_bind_tx_unregister_check to nl_netdev.py. They check that removing a
netdevsim device while a netlink socket holds an RX or TX devmem binding
detaches the dma_buf right away. The commit also adds the dma-buf, udmabuf
and devmem options the tests need to the net selftest config fragment.
> diff --git a/tools/testing/selftests/net/config b/tools/testing/selftests/net/config
> index d4416f8bdcfd1..7a89e2618d4c4 100644
> --- a/tools/testing/selftests/net/config
> +++ b/tools/testing/selftests/net/config
[ ... ]
> @@ -133,6 +136,7 @@ CONFIG_TEST_BLACKHOLE_DEV=m
> CONFIG_TLS=m
> CONFIG_TRACEPOINTS=y
> CONFIG_TUN=y
> +CONFIG_UDMABUF=y
[Severity: Low]
Will CONFIG_UDMABUF=y actually get enabled from this fragment on a minimal
base config? UDMABUF in drivers/dma-buf/Kconfig has these dependencies:
config UDMABUF
bool "userspace dmabuf misc driver"
default n
depends on DMA_SHARED_BUFFER
depends on MEMFD_CREATE || COMPILE_TEST
depends on MMU
CONFIG_SYNC_FILE=y takes care of DMA_SHARED_BUFFER. MEMFD_CREATE has no
default, though, and can only be set directly under EXPERT. Normally it
is turned on because TMPFS or HUGETLBFS selects it, and this fragment
asks for neither.
If the base config has MEMFD_CREATE=n and COMPILE_TEST=n, Kconfig will
quietly drop UDMABUF. Both new tests would then skip in _create_udmabuf()
and never reach the unregister path:
if not os.path.exists("/dev/udmabuf"):
raise KsftSkipEx("/dev/udmabuf is not available")
tools/testing/selftests/bpf/config lists CONFIG_TMPFS=y next to
CONFIG_UDMABUF=y, and tools/testing/selftests/drivers/net/hw/config has
CONFIG_HUGETLBFS=y. Should CONFIG_TMPFS=y be added here as well?
> CONFIG_USER_NS=y
> CONFIG_VETH=y
> CONFIG_VLAN_8021Q=y
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261030083539.777877-1-almasrymina%40google.com
prev parent reply other threads:[~2026-11-01 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 8:35 [PATCH net v5 0/4] net: devmem: fix RX and TX binding teardown on device unregistration Mina Almasry
2026-10-30 8:35 ` [PATCH net v5 1/4] net: devmem: unmap dma_buf synchronously on queue uninstall Mina Almasry
2026-11-01 23:01 ` netdev-bot+sashiko
2026-11-01 23:16 ` Mina Almasry
2026-10-30 8:35 ` [PATCH net v5 2/4] net: devmem: detach TX bindings on NETDEV_UNREGISTER Mina Almasry
2026-11-01 23:01 ` netdev-bot+sashiko
2026-11-01 23:15 ` Mina Almasry
2026-10-30 8:35 ` [PATCH net v5 3/4] netdevsim: support devmem RX and TX bindings Mina Almasry
2026-11-01 23:01 ` netdev-bot+sashiko
2026-10-30 8:35 ` [PATCH net v5 4/4] selftests: net: add devmem RX and TX netdev unregister tests Mina Almasry
2026-11-01 23:01 ` netdev-bot+sashiko [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=179357408797.3131.706180156061595645@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=asml.silence@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=christian.koenig@amd.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dtatulea@nvidia.com \
--cc=dw@davidwei.uk \
--cc=edumazet@kernel.org \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kaifengw@google.com \
--cc=kaiyuanz@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phasta@kernel.org \
--cc=razor@blackwall.org \
--cc=sdf.kernel@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tariqt@nvidia.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®