mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: Greg KH <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: Fri, 27 Feb 2026 01:26:11 -0500	[thread overview]
Message-ID: <bb9ab61c-3bed-4c3d-baf0-0bce4e142292@moonlit-rail.com> (raw)
In-Reply-To: <2026022612-buckskin-surfacing-d854@gregkh>

Greg KH wrote:
> 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.

Bisect complete (from 6.19.3 to 6.19.4)

> e308d4e35ce1e26cd67070a7035ad265662ab9e5 is the first bad commit
> commit e308d4e35ce1e26cd67070a7035ad265662ab9e5
> Author: Pablo Neira Ayuso <pablo@netfilter.org>
> Date:   Wed Jan 21 01:08:45 2026 +0100
> 
>     netfilter: nft_set_rbtree: translate rbtree to array for binary search
>     
>     [ Upstream commit 7e43e0a1141deec651a60109dab3690854107298 ]
>     
>     The rbtree can temporarily store overlapping inactive elements during
>     the transaction processing, leading to false negative lookups.
[snip]

Kris

P.S.  I ran the bisect from 7.0-rc1, so many reboots there, and
       it is fine.  The bug only seems to affect 6.x

  parent reply	other threads:[~2026-02-27  6:26 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
2026-02-27  5:27     ` Kris Karas (Bug Reporting)
2026-02-27  6:26     ` Kris Karas (Bug Reporting) [this message]
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=bb9ab61c-3bed-4c3d-baf0-0bce4e142292@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®