From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH] flow: Set EPOLLFD_ID_DEFAULT on newly allocated flows, not EPOLLFD_ID_INVALID
Date: Tue, 9 Dec 2025 10:36:01 +1100 [thread overview]
Message-ID: <aTdg4ZjiUyHcAXYK@zatzit> (raw)
In-Reply-To: <20251208225400.6a054d22@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
On Mon, Dec 08, 2025 at 10:54:00PM +0100, Stefano Brivio wrote:
> On Mon, 8 Dec 2025 22:28:22 +0100
> Stefano Brivio <sbrivio@redhat.com> wrote:
>
> > We're somehow hitting:
> >
> > ASSERTION FAILED in flow_epollfd (flow.c:362): f->epollid < ((1 << 8) - 1)
> >
> > on an inbound spliced connection, with a single forwarded port, an
> > HTTP server in a Podman container, and a GET request. Reproducer at
> > https://bodhi.fedoraproject.org/updates/FEDORA-2025-93b4eb64c3#comment-4473411
> >
> > printf 'FROM registry.fedoraproject.org/fedora:latest\nRUN /usr/bin/dnf install -y httpd\nEXPOSE 80\nCMD ["-D", "FOREGROUND"]\nENTRYPOINT ["/usr/sbin/httpd"]\n' > Containerfile
> > podman build -t fedora-httpd $(pwd)
> > podman run -d -p 8080:80 localhost/fedora-httpd
> >
> > curl http://localhost:8080
> >
> > I guess we don't set EPOLLFD_ID_DEFAULT early enough on inbound spliced
> > sockets for some reason and we get a socket event while we still have
> > EPOLLFD_ID_INVALID set.
> >
> > As we're not really using epoll identifiers yet, set
> > EPOLLFD_ID_DEFAULT right away on newly allocated flows, while we
> > figure this out.
> >
> > Link: https://bodhi.fedoraproject.org/updates/FEDORA-2025-93b4eb64c3#comment-4473411
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > ---
> > I just merged this, posting for awareness / review.
>
> Ah, never mind, this makes it worse somehow:
>
> 5.6384: Flow 0 (TCP connection (spliced)): SPLICE_CONNECT
> 5.6384: Flow 0 (TCP connection (spliced)): ERROR on epoll_ctl(): No such file or directory
Does this imply you managed to reproduce locally? You hadn't as of
your comment a few after the one linked. I also haven't managed to
reproduce this.
> ...still looking for a workaround / fix.
>
> --
> Stefano
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-08 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 21:28 Stefano Brivio
2025-12-08 21:54 ` Stefano Brivio
2025-12-08 23:36 ` David Gibson [this message]
2025-12-08 23:46 ` Stefano Brivio
2025-12-09 0:01 ` David Gibson
2025-12-09 0:05 ` Stefano Brivio
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=aTdg4ZjiUyHcAXYK@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).