From: David Howells <dhowells@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: dhowells@redhat.com, netdev@vger.kernel.org,
syzbot+f527b971b4bdc8e79f9e@syzkaller.appspotmail.com,
bpf@vger.kernel.org, brauner@kernel.org, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, axboe@kernel.dk, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] udp: Fix __ip_append_data()'s handling of MSG_SPLICE_PAGES
Date: Tue, 01 Aug 2023 21:11:53 +0100 [thread overview]
Message-ID: <1501753.1690920713@warthog.procyon.org.uk> (raw)
In-Reply-To: <64c93109c084e_1c5e3529452@willemb.c.googlers.com.notmuch>
Willem de Bruijn <willemdebruijn.kernel@gmail.com> wrote:
> __ip6_append_data probably needs the same.
Now that's interesting. __ip6_append_data() has a check for this and returns
-EINVAL in this case:
copy = datalen - transhdrlen - fraggap - pagedlen;
if (copy < 0) {
err = -EINVAL;
goto error;
}
but should I bypass that check for MSG_SPLICE_PAGES? It hits the check when
it should be able to get past it. The code seems to go back to prehistoric
times, so I'm not sure why it's there.
For an 8192 MTU, the breaking point is at a send of 8137 bytes. The attached
test program iterates through different send sizes until it hits the point.
David
---
#define _GNU_SOURCE
#include <arpa/inet.h>
#include <fcntl.h>
#include <netinet/ip6.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sys/socket.h>
#include <sys/mman.h>
#include <sys/uio.h>
#define OSERROR(R, S) do { if ((long)(R) == -1L) { perror((S)); exit(1); } } while(0)
int main()
{
struct sockaddr_storage ss;
struct sockaddr_in6 sin6;
void *buffer;
unsigned int tmp;
int pfd[2], sfd;
int res, i;
OSERROR(pipe(pfd), "pipe");
sfd = socket(AF_INET6, SOCK_DGRAM, 0);
OSERROR(sfd, "socket/2");
memset(&sin6, 0, sizeof(sin6));
sin6.sin6_family = AF_INET6;
sin6.sin6_port = htons(7);
#warning set dest IPv6 address below
sin6.sin6_addr.s6_addr32[0] = htonl(0x01020304);
sin6.sin6_addr.s6_addr32[1] = htonl(0x05060708);
sin6.sin6_addr.s6_addr32[2] = htonl(0x00000000);
sin6.sin6_addr.s6_addr32[3] = htonl(0x00000001);
OSERROR(connect(sfd, (struct sockaddr *)&sin6, sizeof(sin6)), "connect");
buffer = mmap(NULL, 1024*1024, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0);
OSERROR(buffer, "mmap");
for (i = 1000; i < 65535; i++) {
printf("%d\n", i);
OSERROR(send(sfd, buffer, i, MSG_MORE), "send");
OSERROR(write(pfd[1], buffer, 8), "write");
OSERROR(splice(pfd[0], 0, sfd, 0, 0x4ffe0ul, 0), "splice");
}
return 0;
}
next prev parent reply other threads:[~2023-08-01 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 15:48 [PATCH net] udp: Fix __ip_append_data()'s handling of MSG_SPLICE_PAGES David Howells
2023-08-01 16:21 ` Willem de Bruijn
2023-08-01 16:57 ` David Howells
2023-08-01 20:11 ` David Howells [this message]
2023-08-01 21:11 ` Willem de Bruijn
2023-08-02 14:27 ` Willem de Bruijn
2023-08-03 2:30 ` 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=1501753.1690920713@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+f527b971b4bdc8e79f9e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willemdebruijn.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).