netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
	netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
	fw@strlen.de, Antonio Ojea <aojea@google.com>
Subject: Re: [PATCH net-next 2/9] selftests: netfilter: nft_queue.sh: sctp coverage
Date: Mon, 26 Aug 2024 19:25:00 -0700	[thread overview]
Message-ID: <20240826192500.32efa22c@kernel.org> (raw)
In-Reply-To: <20240822221939.157858-3-pablo@netfilter.org>

On Fri, 23 Aug 2024 00:19:32 +0200 Pablo Neira Ayuso wrote:
> From: Antonio Ojea <aojea@google.com>
> 
> Test that nfqueue with and without GSO process SCTP packets correctly.
> 
> Joint work with Florian and Pablo.

This is unhappy on a debug kernel in netdev CI:

# 2024/08/26 17:38:31 socat[12451] E write(7, 0x563837a56000, 8192): Cannot send after transport endpoint shutdown
# Binary files /tmp/tmp.ZZAJtF9z9R and /tmp/tmp.hS8W1Te84V differ
# FAIL: lost packets?!

https://netdev-3.bots.linux.dev/vmksft-nf-dbg/results/745281/2-nft-queue-sh/stdout

Works fine on a non-debug kernel tho:

https://netdev-3.bots.linux.dev/vmksft-nf/results/745282/5-nft-queue-sh/stdout

so gotta be some race.

Please follow up soon, I'll disable this test case for now.

  reply	other threads:[~2024-08-27  2:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 22:19 [PATCH net-next 0/9] Netfilter updates for net-next Pablo Neira Ayuso
2024-08-22 22:19 ` [PATCH net-next 1/9] netfilter: nfnetlink_queue: unbreak SCTP traffic Pablo Neira Ayuso
2024-08-26 15:50   ` patchwork-bot+netdevbpf
2024-08-22 22:19 ` [PATCH net-next 2/9] selftests: netfilter: nft_queue.sh: sctp coverage Pablo Neira Ayuso
2024-08-27  2:25   ` Jakub Kicinski [this message]
2024-08-27  9:00     ` [PATCH net-next] selftests: netfilter: nft_queue.sh: reduce test file size for debug build Florian Westphal
2024-08-28 14:48       ` Pablo Neira Ayuso
2024-08-28 22:49       ` Jakub Kicinski
2024-08-29  8:01         ` Florian Westphal
2024-08-29  8:35           ` Paolo Abeni
2024-08-29  8:40       ` patchwork-bot+netdevbpf
2024-08-22 22:19 ` [PATCH net-next 3/9] netfilter: nfnetlink: convert kfree_skb to consume_skb Pablo Neira Ayuso
2024-08-22 22:19 ` [PATCH net-next 4/9] netfilter: nf_tables: store new sets in dedicated list Pablo Neira Ayuso
2024-08-22 22:19 ` [PATCH net-next 5/9] netfilter: nf_tables: do not remove elements if set backend implements .abort Pablo Neira Ayuso
2024-08-22 22:19 ` [PATCH net-next 6/9] netfilter: move nf_ct_netns_get out of nf_conncount_init Pablo Neira Ayuso
2024-08-22 22:19 ` [PATCH net-next 7/9] netfilter: nf_tables: pass context structure to nft_parse_register_load Pablo Neira Ayuso
2024-08-22 22:19 ` [PATCH net-next 8/9] netfilter: nf_tables: allow loads only when register is initialized Pablo Neira Ayuso
2024-08-22 22:19 ` [PATCH net-next 9/9] netfilter: nf_tables: don't initialize registers in nft_do_chain() Pablo Neira Ayuso

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=20240826192500.32efa22c@kernel.org \
    --to=kuba@kernel.org \
    --cc=aojea@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    /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).