From: Bobby Eshleman <bobbyeshleman@gmail.com>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, Mina Almasry <almasrymina@google.com>
Subject: Re: [PATCH net 1/1] net: devmem: prevent net-iov / page mixing
Date: Fri, 24 Jul 2026 12:07:56 -0700 [thread overview]
Message-ID: <amO4DN0oAzkt9n18@devvm29614.prn0.facebook.com> (raw)
In-Reply-To: <5c3c34de-7b34-4122-a792-e91b48858f2f@gmail.com>
On Wed, Jul 22, 2026 at 07:58:27PM +0100, Pavel Begunkov wrote:
> On 7/22/26 18:59, Bobby Eshleman wrote:
> > On Wed, Jul 22, 2026 at 11:58:46AM +0100, Pavel Begunkov wrote:
> > > We should either have net_iov or page backed frags in a single skb,
> > > otherwise it blows up down the stack. Don't allow mixing in
> > > zerocopy_fill_skb_from_devmem().
> > >
> > > Fixes: bd61848900bff ("net: devmem: Implement TX path")
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
> > > ---
> > > net/core/datagram.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/net/core/datagram.c b/net/core/datagram.c
> > > index c285c6465923..35febc1c25fa 100644
> > > --- a/net/core/datagram.c
> > > +++ b/net/core/datagram.c
> > > @@ -712,6 +712,9 @@ zerocopy_fill_skb_from_devmem(struct sk_buff *skb, struct iov_iter *from,
> > > size_t virt_addr, size, off;
> > > struct net_iov *niov;
> > > + if (i && skb_frags_readable(skb))
> > > + return -EEXIST;
> >
> > Are we trying to hit the -EEXIST handler in tcp_sendmsg_locked() so that
> > we start a new skb? If so, I think we might need to plumb this -EEXIST
> > case through skb_zerocopy_iter_stream() too?
>
> Easier to EFAULT. It'd more consistent, and I don't care how tcp takes
> it specifically.
>
> --
> Pavel Begunkov
>
One socket is allowed to queue non-devmem followed by devmem, and EFAULT
will break this case. I think EEXIST is right, just needs to propagate
up.
Best,
Bobby
next prev parent reply other threads:[~2026-07-24 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 10:58 [PATCH net 1/1] net: devmem: prevent net-iov / page mixing Pavel Begunkov
2026-07-22 17:59 ` Bobby Eshleman
2026-07-22 18:58 ` Pavel Begunkov
2026-07-24 19:07 ` Bobby Eshleman [this message]
2026-07-22 19:49 ` Mina Almasry
2026-07-22 20:20 ` Pavel Begunkov
2026-07-23 17:24 ` Bobby Eshleman
2026-07-23 18:35 ` Mina Almasry
2026-07-23 23:10 ` Bobby Eshleman
2026-07-24 17:26 ` Mina Almasry
2026-07-24 18:52 ` Bobby Eshleman
2026-07-24 17:25 ` Mina Almasry
2026-07-24 17:40 ` Mina Almasry
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=amO4DN0oAzkt9n18@devvm29614.prn0.facebook.com \
--to=bobbyeshleman@gmail.com \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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