From: Stanislav Fomichev <sdf.kernel@gmail.com>
To: netdev-bot+sashiko@kernel.org
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
sdf@fomichev.me, bobbyeshleman@meta.com, almasrymina@google.com,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH net-next v3 2/3] net: devmem: embed net_iov_area in binding
Date: Mon, 21 Sep 2026 09:58:19 -0700 [thread overview]
Message-ID: <76355a60e1b7e5d664d956e7a06c5900@gmail.com> (raw)
In-Reply-To: <178993807923.2160803.4802601925465816308@kernel.org>
> [Severity: Medium]
> Can this loop in net_devmem_bind_dmabuf() write past
> binding->area.niovs[], binding->freelist[] and binding->tx_vec[]?
I do not think this is real. io_uring checks this because I think
area_reg->len is from userspace. For dmabufs, len should be sum(sg->len).
You yourself claim: The in-tree exporters I looked at (udmabuf, dma-heaps,
drm_prime) do build SG tables totalling dmabuf->size...
next prev parent reply other threads:[~2026-09-21 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 18:11 [PATCH net-next v3 0/3] net: devmem: remove gen_pool from dma-buf allocations Stanislav Fomichev
2026-09-17 18:11 ` [PATCH net-next v3 1/3] net: devmem: replace gen_pool with freelist Stanislav Fomichev
2026-09-20 21:01 ` netdev-bot+sashiko
2026-09-21 16:58 ` Stanislav Fomichev
2026-09-21 23:29 ` Jakub Kicinski
2026-09-21 23:34 ` Mina Almasry
2026-09-17 18:11 ` [PATCH net-next v3 2/3] net: devmem: embed net_iov_area in binding Stanislav Fomichev
2026-09-20 21:01 ` netdev-bot+sashiko
2026-09-21 16:58 ` Stanislav Fomichev [this message]
2026-09-17 18:11 ` [PATCH net-next v3 3/3] net: devmem: batch net_iov allocations into the page_pool cache Stanislav Fomichev
2026-09-21 23:50 ` [PATCH net-next v3 0/3] net: devmem: remove gen_pool from dma-buf allocations patchwork-bot+netdevbpf
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=76355a60e1b7e5d664d956e7a06c5900@gmail.com \
--to=sdf.kernel@gmail.com \
--cc=almasrymina@google.com \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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®