netdev - Re: Fwd: inet6_sock_destruct->inet_sock

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] [day] [month] [year] [list]

Date: Tue, 21 Nov 2023 16:41:17 +0100
From: "Linux regression tracking #update (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Muhammad Usama Anjum <usama.anjum@...labora.com>,
 Bagas Sanjaya <bagasdotme@...il.com>, "David S. Miller"
 <davem@...emloft.net>, David Ahern <dsahern@...nel.org>,
 Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>
Cc: Linux Networking <netdev@...r.kernel.org>, Linux BPF
 <bpf@...r.kernel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Regressions <regressions@...ts.linux.dev>
Subject: Re: Fwd: inet6_sock_destruct->inet_sock_destruct trigger Call Trace

On 29.08.23 15:07, Muhammad Usama Anjum wrote:
> On 6/16/23 5:43 PM, Bagas Sanjaya wrote:
>> I notice a regression report on Bugzilla [1]. Quoting from it:
> [...]
>>> When the IPv6 address or NIC configuration changes, the following kernel warnings may be triggered:
> [...]
>>> Thu Jun 15 09:02:31 2023 daemon.info : 09[KNL] interface utun deleted
> [...]
>> #regzbot introduced: v6.1.27..v6.1.32 https://bugzilla.kernel.org/show_bug.cgi?id=217555
>> #regzbot title: kernel warning (oops) at inet_sock_destruct
> The same warning has been seen on 4.14, 5.15, 6.1 and latest mainline.
>
> This WARN_ON is present from 2008.

Hmmm, the commit that according to syzkaller's bisection caused this is
not in those series. So I assume the bisection went sideways.

And the reporter of the bugzilla ticket never bisected this either.
Wondering if it started to show up there due to small unrelated timing
changes.

Not totally sure, but it seems like this in the end is not a real
regression or one we can't do anything about. Thus removing this from
the tracking; if anyone disagrees, please holler.

#regzbot inconclusive: likely an older problem
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.