public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
Cc: akpm@linux-foundation.org, jslaby@suse.cz,
	linux-kernel@vger.kernel.org, lwn@lwn.net,
	stable@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 6.19.4 - Oops, regression
Date: Thu, 26 Feb 2026 20:56:59 -0800	[thread overview]
Message-ID: <2026022612-buckskin-surfacing-d854@gregkh> (raw)
In-Reply-To: <eb2d1da9-0b4b-4887-83a4-0e2a65e703aa@moonlit-rail.com>

On Thu, Feb 26, 2026 at 11:46:02PM -0500, Kris Karas (Bug Reporting) wrote:
> GregKH wrote:
> > I'm announcing the release of the 6.19.4 kernel.
> > All users of the 6.19 kernel series must upgrade.
> 
> Just tried 6.19.4 (and 6.18.14) and am getting a repeatable Oops right when
> networking is initialized, likely when nft is loading its ruleset from
> /etc/nftables/*.conf
> 
> Once the nft Oops triggers, other processes start to throw errors with
> memory allocate/free, resulting very quickly in an unusable system. I have
> several systems that run iptables, which are unaffected, notably my border
> router with 400+ rules. I have three systems running nftables, one of which
> is affected, the affected one having the more sophisticated nft ruleset
> (bridging, 802.1Q, etc).

Ick, not good.  Can you do 'git bisect' to find the problem commit?  As
you have a pretty reliable reproducer it should go pretty fast.

But first, does 7.0-rc1 work or also crash the same way?

thanks,

greg k-h

  reply	other threads:[~2026-02-27  4:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 23:14 Linux 6.19.4 Greg Kroah-Hartman
2026-02-26 23:14 ` Greg Kroah-Hartman
2026-02-27  4:46 ` Linux 6.19.4 - Oops, regression Kris Karas (Bug Reporting)
2026-02-27  4:56   ` Greg KH [this message]
2026-02-27  5:27     ` Kris Karas (Bug Reporting)
2026-02-27  6:26     ` Kris Karas (Bug Reporting)
2026-02-27 12:09       ` Genes Lists
2026-02-27 13:18         ` Genes Lists
2026-02-27 13:32           ` Greg KH
2026-02-27 13:59             ` Genes Lists
2026-02-27 14:44               ` Genes Lists
2026-02-27 18:51                 ` Philip Müller
2026-02-27 20:17                   ` Greg KH
2026-02-27 21:01         ` Kris Karas (Bug Reporting)
2026-02-27 21:20           ` Genes Lists

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=2026022612-buckskin-surfacing-d854@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bugs-a21@moonlit-rail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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