netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Sitnicki <jakub@cloudflare.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org,  kernel-team@cloudflare.com
Subject: Re: [FYI] Input route ref count underflow since probably 6.6.22
Date: Tue, 02 Jul 2024 16:21:56 +0200	[thread overview]
Message-ID: <87wmm3euwr.fsf@cloudflare.com> (raw)
In-Reply-To: <20240701163826.76558147@kernel.org> (Jakub Kicinski's message of "Mon, 1 Jul 2024 16:38:26 -0700")

On Mon, Jul 01, 2024 at 04:38 PM -07, Jakub Kicinski wrote:
> On Fri, 28 Jun 2024 13:10:53 +0200 Jakub Sitnicki wrote:
>> We've observed an unbalanced dst_release() on an input route in v6.6.y.
>> First noticed in 6.6.22. Or at least that is how far back our logs go.
>> 
>> We have just started looking into it and don't have much context yet,
>> except that:
>> 
>> 1. the issue is architecture agnostic, seen both on x86_64 and arm64;
>> 2. the backtrace, we realize, doesn't point to the source of problem,
>>    it's just where the ref count underflow manifests itself;
>> 3. while have out-of-tree modules, they are for the crypto subsystem.
>> 
>> We will follow up as we collect more info on this, but we would
>> appreciate any hints or pointers to potential suspects, if anything
>> comes to mind.
>
> Hi! Luck would have it the same crash landed on my desk.
> Did you manage to narrow it down?

Nothing yet. Will keep you posted.

  reply	other threads:[~2024-07-02 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 11:10 [FYI] Input route ref count underflow since probably 6.6.22 Jakub Sitnicki
2024-07-01 23:38 ` Jakub Kicinski
2024-07-02 14:21   ` Jakub Sitnicki [this message]
2025-01-13 12:02     ` Jakub Sitnicki

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=87wmm3euwr.fsf@cloudflare.com \
    --to=jakub@cloudflare.com \
    --cc=kernel-team@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=netdev@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).