kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 220200] Kernel crash with WARNING: CPU: 17 PID: 4510 at lib/refcount.c:28 refcount_warn_saturate+0xd8/0xe0
Date: Mon, 09 Jun 2025 18:27:29 +0000	[thread overview]
Message-ID: <bug-220200-28872-gtRVfqlbey@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220200-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220200

gs.thiruus@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|ANSWERED                    |---

--- Comment #2 from gs.thiruus@gmail.com ---
Thanks for your response. 

Though the warning and RIP info matching with the one shared in the thread
(https://github.com/flatcar/Flatcar/issues/427) which you shared, 
WARNING: CPU: 10 PID: 13791 at lib/refcount.c:28
refcount_warn_saturate+0xa6/0xf0 
RIP: 0010:refcount_warn_saturate+0xa6/0xf0

I see the call trace observed in our setup, not matching.

as per the link shared, fix provided in netfilter module. 

Could you please share more details how will it help to fix the trace observed
in our setup?

Thanks

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-06-09 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  0:00 [Bug 220200] New: Kernel crash with WARNING: CPU: 17 PID: 4510 at lib/refcount.c:28 refcount_warn_saturate+0xd8/0xe0 bugzilla-daemon
2025-06-06  0:02 ` [Bug 220200] " bugzilla-daemon
2025-06-06  8:14 ` bugzilla-daemon
2025-06-09 18:27 ` bugzilla-daemon [this message]
2025-06-11  5:00 ` bugzilla-daemon
2025-06-18 20:29 ` bugzilla-daemon

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=bug-220200-28872-gtRVfqlbey@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).