MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: MPTCP Linux <mptcp@lists.linux.dev>, Gang Yan <gang.yan@linux.dev>
Subject: Re: CI failures on nipa
Date: Fri, 14 Aug 2026 16:08:02 +0200	[thread overview]
Message-ID: <28af8e56-9cc7-4122-8150-a7cb9717fc77@kernel.org> (raw)
In-Reply-To: <dab17176-51d7-40be-ae95-bfed9ab6691a@redhat.com>

On 14/08/2026 13:33, Paolo Abeni wrote:
> On 8/13/26 11:15 AM, Matthieu Baerts wrote:
>> On 13/08/2026 09:57, Paolo Abeni wrote:
>>> Also I think mptcp_lib_wait_timeout completes too late (after ~60 secs),
>>> when the listener already bailed out due to accept timeout (after ~30
>>> secs), so it does not show any info on the listener side. I fear it may
>>> also race with the actuall `timeout` command completion showing socket
>>> states after the user-space program completion.
>>
>> Do you mean you would like to have mptcp_lib_wait_timeout wait for less
>> than the accept timeout?
> 
> Ideally yes, but I'm not sure which time would be ideal...
What about the following "workaround" I just sent?

https://lore.kernel.org/20260814-sft-mptcp-stats-b4-close-v1-1-2945a591be7e@kernel.org

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2026-08-14 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13  7:57 CI failures on nipa Paolo Abeni
2026-08-13  8:59 ` gang.yan
2026-08-13  9:20   ` Matthieu Baerts
2026-08-13  9:37     ` gang.yan
2026-08-13  9:15 ` Matthieu Baerts
2026-08-14 11:33   ` Paolo Abeni
2026-08-14 14:08     ` Matthieu Baerts [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=28af8e56-9cc7-4122-8150-a7cb9717fc77@kernel.org \
    --to=matttbe@kernel.org \
    --cc=gang.yan@linux.dev \
    --cc=mptcp@lists.linux.dev \
    --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