linux-kernel - Re: Unexplainable packet drop starting at v6.4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230725174712.66a809c4@kernel.org>
Date:   Tue, 25 Jul 2023 17:47:12 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Andrzej Kacprowski <andrzej.kacprowski@...ux.intel.com>,
        Krystian Pradzynski <krystian.pradzynski@...ux.intel.com>,
        Stanislaw Gruszka <stanislaw.gruszka@...ux.intel.com>,
        Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com>,
        Oded Gabbay <ogabbay@...nel.org>,
        Jesse Brandeburg <jesse.brandeburg@...el.com>,
        Tony Nguyen <anthony.l.nguyen@...el.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Paolo Abeni <pabeni@...hat.com>,
        "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>, hq.dev+kernel@...fc.xyz,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux DRI Development <dri-devel@...ts.freedesktop.org>,
        Linux Networking <netdev@...r.kernel.org>,
        Linux Intel Ethernet Drivers 
        <intel-wired-lan@...ts.osuosl.org>
Subject: Re: Unexplainable packet drop starting at v6.4

On Wed, 26 Jul 2023 06:50:52 +0700 Bagas Sanjaya wrote:
> This time, the bisection points out to v6.4 networking pull, so:
> 
> #regzbot introduced: 6e98b09da931a0

Ask the reporter to test 9b78d919632b, i.e. the tip of net-next before
the merge. It seems quite unlikely that the merge itself is the problem.