public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] tcp, flow: Fix some error paths which didn't clean up flows properly
Date: Fri, 7 Jun 2024 20:49:17 +0200	[thread overview]
Message-ID: <20240607204917.70dd6cf4@elisabeth> (raw)
In-Reply-To: <20240607015524.1633407-1-david@gibson.dropbear.id.au>

On Fri,  7 Jun 2024 11:55:24 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> Flow table entries need to be fully initialised before returning to the
> main epoll loop.  Commit 0060acd1 ("flow: Clarify and enforce flow state
> transitions") now enforces that: once a flow is allocated we must either
> cancel it, or activate it before returning to the main loop, or we will hit
> an ASSERT().
> 
> Some error paths in tcp_conn_from_tap() weren't correctly updated for this
> requirement - we can exit with a flow entry incompletely initialised.
> Correct that by cancelling the flows in those situations.
> 
> I don't have enough information to be certain if this is the cause for
> podman bug 22925, but it plausibly could be.
> 
> Fixes: 0060acd1 ("flow: Clarify and enforce flow state transitions")
> Link: https://github.com/containers/podman/issues/22925
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Applied.

-- 
Stefano


      reply	other threads:[~2024-06-07 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  1:55 [PATCH] tcp, flow: Fix some error paths which didn't clean up flows properly David Gibson
2024-06-07 18:49 ` Stefano Brivio [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=20240607204917.70dd6cf4@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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).