All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Dan Moulding <dan@danm.net>
Cc: netfilter-devel@vger.kernel.org, pablo@netfilter.org,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] v6.16 system hangs (bisected to nf_conntrack fix)
Date: Thu, 31 Jul 2025 17:49:53 +0200	[thread overview]
Message-ID: <aIuQoUQQnFMyvJJs@strlen.de> (raw)
In-Reply-To: <aIkHAZjudod05WaR@strlen.de>

Florian Westphal <fw@strlen.de> wrote:
> Dan Moulding <dan@danm.net> wrote:
> > Ok. I just tried reverting only the changes to nf_conntrack_core.c and
> > the hang no longer occurs. This is on top of 6.16.
> 
> Strange.  Can you completely revert 2d72afb340657f03f7261e9243b44457a9228ac7
> and then apply this patch instead?

Any news?  If you don't have the time to test, could you please share
kernel config or at least some details like CONFIG_PREEMPT settings, if
this uses kasan, kcsan etc.?

I'm asking because I still cannot reproduce any hangs, so I assume that
there is some significant difference between our setups.
While I could ask for a blank revert, that would get back the bug I
was trying to fix and I dislike doing so without understanding the cause
of the new bug first.

Are you using anything more excotic, say, conntrackd, conntrack
helpers, synproxy, or anything like that?

I was able to produce a memory leak by running conntrack_resize.sh
selftest in a loop, but its unrelated bug in ctnetlink.

I will submit a patch later after some more testing.

  reply	other threads:[~2025-07-31 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 23:25 [REGRESSION] v6.16 system hangs (bisected to nf_conntrack fix) Dan Moulding
2025-07-28 23:47 ` Florian Westphal
2025-07-29  0:25   ` Florian Westphal
2025-07-29 17:02   ` Dan Moulding
2025-07-29 17:38     ` Florian Westphal
2025-07-31 15:49       ` Florian Westphal [this message]
2025-07-31 19:49         ` Dan Moulding
2025-08-30  3:48           ` Dan Moulding

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=aIuQoUQQnFMyvJJs@strlen.de \
    --to=fw@strlen.de \
    --cc=dan@danm.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.