linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Linux Networking <netdev@vger.kernel.org>,
	Linux BPF <bpf@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Fwd: inet6_sock_destruct->inet_sock_destruct trigger Call Trace
Date: Tue, 21 Nov 2023 16:41:17 +0100	[thread overview]
Message-ID: <0a594a11-d345-48c3-a651-08ea80ab76a1@leemhuis.info> (raw)
In-Reply-To: <c3a5d08e-9c7c-4888-916a-ba4bd22a3319@collabora.com>

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.


      reply	other threads:[~2023-11-21 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 12:43 Fwd: inet6_sock_destruct->inet_sock_destruct trigger Call Trace Bagas Sanjaya
2023-08-29 13:07 ` Muhammad Usama Anjum
2023-11-21 15:41   ` Linux regression tracking #update (Thorsten Leemhuis) [this message]

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=0a594a11-d345-48c3-a651-08ea80ab76a1@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=bagasdotme@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=usama.anjum@collabora.com \
    /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;
as well as URLs for NNTP newsgroup(s).