Netdev List
 help / color / mirror / Atom feed
From: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
To: David Howells <dhowells@redhat.com>,
	Marc Dionne <marc.dionne@auristor.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	linux-afs@lists.infradead.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [BUG] rxrpc/afs: leaked peer during netns teardown
Date: Sun,  5 Jul 2026 02:54:13 -0400	[thread overview]
Message-ID: <20260705065415.120034-1-shuangpeng.kernel@gmail.com> (raw)

Hi,

I can reproduce an RxRPC leaked-peer warning during network namespace
teardown after adding an AFS cell.

Reproducer:

  dmesg -C

  unshare -n sh -c '
          ip link set lo up 2>/dev/null || true
          echo "add reprocell 127.0.0.1" > /proc/fs/afs/cells
          cat /proc/net/rxrpc/peers
  '

  sleep 2
  dmesg | grep "Leaked peer"

Observed output:

  Proto Local                                           Remote                                          Use SST   Maxd LastUse      RTT      RTO
  UDP   [::]:7001                                       127.0.0.1:7003                                    1  128  1440     37s       -1        0
  [   37.969040] rxrpc: Leaked peer 61 {1} 127.0.0.1:7003

Tested on:

  commit 9fbbf69eab3417732ec2adf93e42e507351dd80a
  Linux 7.1.0-13212-g9fbbf69eab34
  CONFIG_NET_NS=y
  CONFIG_AF_RXRPC=y
  CONFIG_AFS_FS=y

Thanks.

                 reply	other threads:[~2026-07-05  6:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260705065415.120034-1-shuangpeng.kernel@gmail.com \
    --to=shuangpeng.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --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