The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, thorsten.blum@linux.dev,
	akpm@linux-foundation.org, andriy.shevchenko@intel.com,
	rdunlap@infradead.org, robert.olsson@its.uu.se,
	stephen@networkplumber.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] net: pktgen: fix proc entry use-after-free
Date: Fri, 24 Jul 2026 23:40:05 +0000	[thread overview]
Message-ID: <178493640576.3354511.539340145815216251.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260719145740.2888967-1-nicoyip.dev@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun, 19 Jul 2026 22:57:40 +0800 you wrote:
> pktgen_change_name() replaces pkt_dev->entry while holding t->if_lock.
> pktgen_remove_device() removes the same entry before
> _rem_dev_from_if_list() takes that lock.
> 
> This allows the following interleaving:
> 
>   CPU 0 (NETDEV_CHANGENAME)       CPU 1 (kpktgend)
>   if_lock(t)
>   proc_remove(pkt_dev->entry)
>                                   proc_remove(pkt_dev->entry)
>   pkt_dev->entry = proc_create_data(...)
>   if_unlock(t)
> 
> [...]

Here is the summary with links:
  - net: pktgen: fix proc entry use-after-free
    https://git.kernel.org/netdev/net/c/817ff6efdb7f

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



      parent reply	other threads:[~2026-07-24 23:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-19 14:57 [PATCH] net: pktgen: fix proc entry use-after-free Chengfeng Ye
2026-07-24 13:24 ` Simon Horman
2026-07-24 23:40 ` 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=178493640576.3354511.539340145815216251.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicoyip.dev@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=robert.olsson@its.uu.se \
    --cc=stable@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=thorsten.blum@linux.dev \
    /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