The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <john.cs.hey@gmail.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
	<edumazet@google.com>, <horms@kernel.org>, <kuba@kernel.org>,
	<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	<pabeni@redhat.com>
Subject: Re: [Bug] "WARNING in should_fail_ex" in Linux kernel v6.14
Date: Wed, 21 May 2025 11:50:22 -0700	[thread overview]
Message-ID: <20250521185026.56042-1-kuniyu@amazon.com> (raw)
In-Reply-To: <CAP=Rh=N4QcPLWQ2dqUHmKYeEhig3Cbi-3N8Q4-7qGT00htXrVw@mail.gmail.com>

From: John <john.cs.hey@gmail.com>
Date: Wed, 21 May 2025 22:13:15 +0800
> Dear Linux Kernel Maintainers,
> 
> I hope this message finds you well.
> 
> I am writing to report a potential vulnerability I encountered during
> testing of the Linux Kernel version v6.14.
> 
> Git Commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557 (tag: v6.14)
> 
> Bug Location: net/ipv4/ipmr.c:440 ipmr_free_table net/ipv4/ipmr.c:440
> 
> Bug report: https://pastebin.com/xkfF5DBt
> 
> Complete log: https://pastebin.com/uCfqY4D8
> 
> Entire kernel config: https://pastebin.com/MRWGr3nv
> 
> Root Cause Analysis:
> The kernel warning is triggered in ipmr_free_table() at
> net/ipv4/ipmr.c:440, where the multicast routing table (mr_table) is
> being freed during network namespace exit (ipmr_rules_exit).
> The warning indicates that the multicast forwarding cache count
> (mfc_cache_cnt) is non-zero, implying that resources were not
> correctly cleaned up prior to netns teardown.
> This suggests a possible bug in reference counting or teardown logic
> of the IPv4 multicast routing infrastructure.
> Additionally, the environment is running with fail_usercopy fault
> injection enabled, which deliberately triggers copy-from-user failures
> to test kernel error paths.
> While these failures are expected, they may interact with multicast
> socket setup/teardown paths, exacerbating latent issues.

I think this was fixed by

commit c46286fdd6aa1d0e33c245bcffe9ff2428a777bd
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu May 15 18:49:26 2025 +0200

    mr: consolidate the ipmr_can_free_table() checks.

      reply	other threads:[~2025-05-21 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21 14:13 [Bug] "WARNING in should_fail_ex" in Linux kernel v6.14 John
2025-05-21 18:50 ` Kuniyuki Iwashima [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=20250521185026.56042-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=john.cs.hey@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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