The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Charalampos Mitrodimas <charmitro@posteo.net>
Cc: jmaloy@redhat.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	wangliang74@huawei.com, netdev@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	syzbot+f0c4a4aba757549ae26c@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2] net: tipc: fix refcount warning in tipc_aead_encrypt
Date: Thu, 29 May 2025 10:10:29 +0000	[thread overview]
Message-ID: <174851342900.3214659.3602583798283655289.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250527-net-tipc-warning-v2-1-df3dc398a047@posteo.net>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 27 May 2025 16:35:44 +0000 you wrote:
> syzbot reported a refcount warning [1] caused by calling get_net() on
> a network namespace that is being destroyed (refcount=0). This happens
> when a TIPC discovery timer fires during network namespace cleanup.
> 
> The recently added get_net() call in commit e279024617134 ("net/tipc:
> fix slab-use-after-free Read in tipc_aead_encrypt_done") attempts to
> hold a reference to the network namespace. However, if the namespace
> is already being destroyed, its refcount might be zero, leading to the
> use-after-free warning.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: tipc: fix refcount warning in tipc_aead_encrypt
    https://git.kernel.org/netdev/net/c/f29ccaa07cf3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-05-29 10:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 16:35 [PATCH net v2] net: tipc: fix refcount warning in tipc_aead_encrypt Charalampos Mitrodimas
2025-05-28  1:30 ` Tung Quang Nguyen
2025-05-29 10:10 ` patchwork-bot+netdevbpf [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=174851342900.3214659.3602583798283655289.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=charmitro@posteo.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+f0c4a4aba757549ae26c@syzkaller.appspotmail.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=wangliang74@huawei.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