From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: gregkh@linuxfoundation.org
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 23:46:02 -0500 [thread overview]
Message-ID: <eb2d1da9-0b4b-4887-83a4-0e2a65e703aa@moonlit-rail.com> (raw)
In-Reply-To: <2026022657-clambake-mountable-8175@gregkh>
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).
Kris
---------- Snip ----------
Here's the output from dmesg:
> 8021q: adding VLAN 0 to HW filter on device eth0
> ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade
> rev:0 func:0 (0x1001)
> igb 0000:0a:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex,
> Flow Control: RX
> BUG: unable to handle page fault for address: 000000010000001d
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 126bd2067 P4D 126bd2067 PUD 0
> Oops: Oops: 0000 [#1] SMP
> CPU: 12 UID: 0 PID: 1184 Comm: nft Not tainted 6.19.4 #1 PREEMPTLAZY
> Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470
> Taichi, BIOS P10.41 04/14/2025
> RIP: 0010:__kmalloc_noprof+0x1d0/0x3c0
> Code: 2e 85 5b 01 48 8b 50 08 48 83 78 10 00 48 8b 38 0f 84 b7 01 00
> 00 48 85 ff 0f 84 ae 01 00 00 41 8b 41 30 49 8b 31 48 8d 4a 20 <48> 8b
> 1c 07 48 89 f8 65 48 0f c7 0e 75 c1 41 8b 41 30 0f 0d 0c 03
> RSP: 0018:ffffc9000111f5e0 EFLAGS: 00010202
> RAX: 0000000000000020 RBX: ffff88810592e200 RCX: 0000000000042a4c
> RDX: 0000000000042a2c RSI: ffffffff82af08e0 RDI: 00000000fffffffd
> RBP: ffffc9000111f620 R08: 0000000000000030 R09: ffff888100044300
> R10: 0000000000400dc0 R11: 0000000000000030 R12: 0000000000000000
> R13: ffffc9000111f70e R14: ffffffffa06737f4 R15: ffffc9000111f7b8
> FS: 00007fc46c393740(0000) GS:ffff88907c036000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000000010000001d CR3: 0000000126bd5000 CR4: 0000000000350ef0
> Call Trace:
> <TASK>
> ? nla_memcpy+0x29/0x60
> nft_set_elem_init+0x44/0x140 [nf_tables]
> nft_add_set_elem+0xa77/0x14e0 [nf_tables]
> ? vsnprintf+0x3ac/0x5a0
> ? __nft_trans_set_add+0xb6/0x120 [nf_tables]
> ? nla_strcmp+0x10/0x60
> nf_tables_newsetelem+0x19e/0x270 [nf_tables]
> nfnetlink_rcv_batch+0x582/0x8e0
> ? netlink_alloc_large_skb+0x3a/0xa0
> ? __alloc_frozen_pages_noprof+0x148/0x280
> nfnetlink_rcv+0x172/0x190
> netlink_unicast+0x1d4/0x2b0
> netlink_sendmsg+0x1ed/0x410
> __sock_sendmsg+0x2b/0x40
> ____sys_sendmsg+0x1fb/0x220
> ? copy_msghdr_from_user+0xe5/0x170
> ___sys_sendmsg+0x78/0xc0
> ? security_capable+0x25/0x50
> ? release_sock+0x14/0x80
> ? sk_setsockopt+0x36c/0x1590
> ? __handle_mm_fault+0x975/0x1660
> ? do_sock_getsockopt+0x1a2/0x1d0
> __sys_sendmsg+0x66/0xc0
> do_syscall_64+0x4e/0xe30
> entry_SYSCALL_64_after_hwframe+0x4b/0x53
> RIP: 0033:0x7fc46c0981f7
> Code: 08 74 44 b8 04 00 00 00 48 8b 15 ec 6b 16 00 64 89 02 48 c7 c2
> ff ff ff ff 48 83 c4 10 48 89 d0 5b c3 90 48 8b 44 24 20 0f 05 <48> 63
> d0 3d 00 f0 ff ff 77 0f 48 83 c4 10 48 89 d0 5b c3 66 0f 1f
> RSP: 002b:00007ffec97ae5f0 EFLAGS: 00000202 ORIG_RAX: 000000000000002e
> RAX: ffffffffffffffda RBX: 0000000009146b20 RCX: 00007fc46c0981f7
> RDX: 0000000000000000 RSI: 00007ffec97bf6d0 RDI: 0000000000000003
> RBP: 00007ffec97bf7c0 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffec97bf810
> R13: 0000000000013800 R14: 0000000000000003 R15: 00007ffec97ae640
> </TASK>
> Modules linked in: nft_meta_bridge nf_conntrack_bridge nft_log
> nft_limit nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_ct tap
> nf_tables ip_set ip6table_security iptable_security ip6table_raw
> iptable_raw ip6table_mangle iptabl
> e_mangle ip6table_nat iptable_nat ip6table_filter ip6_tables
> iptable_filter ip_tables btusb btrtl btintel btbcm btmtk bluetooth
> sd_mod iwlmvm uas usb_storage mac80211 iwlwifi ahci
> snd_hda_codec_alc882 libahci snd_hda_codec_realtek
> _lib cfg80211 igb libata rfkill snd_hda_codec_generic i2c_algo_bit
> snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep
> snd_pcm snd_timer snd soundcore ee1004 acpi_cpufreq gpio_amdpt
> gpio_generic processor joydev bi
> nfmt_misc
> CR2: 000000010000001d
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:__kmalloc_noprof+0x1d0/0x3c0
> Code: 2e 85 5b 01 48 8b 50 08 48 83 78 10 00 48 8b 38 0f 84 b7 01 00
> 00 48 85 ff 0f 84 ae 01 00 00 41 8b 41 30 49 8b 31 48 8d 4a 20 <48> 8b
> 1c 07 48 89 f8 65 48 0f c7 0e 75 c1 41 8b 41 30 0f 0d 0c 03
> RSP: 0018:ffffc9000111f5e0 EFLAGS: 00010202
> RAX: 0000000000000020 RBX: ffff88810592e200 RCX: 0000000000042a4c
> RDX: 0000000000042a2c RSI: ffffffff82af08e0 RDI: 00000000fffffffd
> RBP: ffffc9000111f620 R08: 0000000000000030 R09: ffff888100044300
> R10: 0000000000400dc0 R11: 0000000000000030 R12: 0000000000000000
> R13: ffffc9000111f70e R14: ffffffffa06737f4 R15: ffffc9000111f7b8
> FS: 00007fc46c393740(0000) GS:ffff88907c036000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000000010000001d CR3: 0000000126bd5000 CR4: 0000000000350ef0
> note: nft[1184] exited with irqs disabled
next prev parent reply other threads:[~2026-02-27 4:58 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 ` Kris Karas (Bug Reporting) [this message]
2026-02-27 4:56 ` Linux 6.19.4 - Oops, regression Greg KH
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=eb2d1da9-0b4b-4887-83a4-0e2a65e703aa@moonlit-rail.com \
--to=bugs-a21@moonlit-rail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®