public inbox for netfilter-devel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: Scott Mitchell <scott.k.mitch1@gmail.com>,
	netfilter-devel@vger.kernel.org
Subject: Re: nfnetlink_queue crashes kernel
Date: Mon, 6 Apr 2026 19:10:31 +0200	[thread overview]
Message-ID: <adPpAPURumLBRrp8@strlen.de> (raw)
In-Reply-To: <867c1ae1-66b4-4584-985a-38a4f7d55925@suse.de>

Fernando Fernandez Mancera <fmancera@suse.de> wrote:
> On 4/4/26 11:40 AM, Florian Westphal wrote:
> > I had a go at adding a stress test but its not
> > triggering for me even if i run it for 10m.
> 
> Bingo! I modified the test you attached a bit to include your 
> suggestions and I got the splat on virtme-ng when running the test. See 
> the whole splat attached below.
> I am going to test your proposed patch and check out the results. In 
> addition I will do some cleanup and send this as a formal nf-next patch.

Thanks Fernando, this helps a lot.

Given the revert isn't clean and the per-queue ht fix isn't larger
than the (modified...) revert I am still considering to apply the fix
to nf instead of revert + nf-next defer.

  reply	other threads:[~2026-04-06 17:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 12:22 nfnetlink_queue crashes kernel Florian Westphal
2026-04-03 13:45 ` Florian Westphal
2026-04-03 15:55   ` Scott Mitchell
2026-04-03 19:14     ` Florian Westphal
2026-04-03 23:57   ` Fernando Fernandez Mancera
2026-04-04  9:40     ` Florian Westphal
2026-04-06 12:54       ` Fernando Fernandez Mancera
2026-04-06 17:10         ` Florian Westphal [this message]
2026-04-06 20:04           ` Fernando Fernandez Mancera
2026-04-06 14:01   ` Fernando Fernandez Mancera
2026-04-03 13:59 ` Florian Westphal
2026-04-03 14:02 ` 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=adPpAPURumLBRrp8@strlen.de \
    --to=fw@strlen.de \
    --cc=fmancera@suse.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=scott.k.mitch1@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