From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net 0/4] net: drop_monitor: fix concurrency issues, preemption warning, and buffer overrun
Date: Wed, 16 Sep 2026 01:10:05 +0000 [thread overview]
Message-ID: <178952100513.2346086.3291685247493878437.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910204612.3762015-1-edumazet@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Sep 2026 20:46:08 +0000 you wrote:
> This series addresses several issues discovered in the drop_monitor subsystem:
>
> Patch 1 adds missing tracepoint unregistration synchronization to the
> net_dm_trace_on_set() error unwind path, preventing in-flight probes
> from scheduling work after the module reference has been dropped.
>
> Patch 2 resolves a race condition during monitoring teardown where per-CPU
> timers can be re-armed after deletion if a concurrent worker encounters a
> memory allocation failure, switching to timer_shutdown_sync().
>
> [...]
Here is the summary with links:
- [net,1/4] drop_monitor: synchronize tracepoint unregistration on error path
https://git.kernel.org/netdev/net/c/6a038ef2b579
- [net,2/4] drop_monitor: use timer_shutdown_sync() to prevent timer rearming during teardown
https://git.kernel.org/netdev/net/c/c391a40f7188
- [net,3/4] drop_monitor: use raw_cpu_ptr() in tracepoint probes
https://git.kernel.org/netdev/net/c/c19b7d35086b
- [net,4/4] drop_monitor: fix out-of-bounds write in reset_per_cpu_data()
https://git.kernel.org/netdev/net/c/439f392084f8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-16 1:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 20:46 [PATCH net 0/4] net: drop_monitor: fix concurrency issues, preemption warning, and buffer overrun Eric Dumazet
2026-09-10 20:46 ` [PATCH net 1/4] drop_monitor: synchronize tracepoint unregistration on error path Eric Dumazet
2026-09-11 9:46 ` Hangbin Liu
2026-09-10 20:46 ` [PATCH net 2/4] drop_monitor: use timer_shutdown_sync() to prevent timer rearming during teardown Eric Dumazet
2026-09-11 9:57 ` Hangbin Liu
2026-09-10 20:46 ` [PATCH net 3/4] drop_monitor: use raw_cpu_ptr() in tracepoint probes Eric Dumazet
2026-09-10 20:46 ` [PATCH net 4/4] drop_monitor: fix out-of-bounds write in reset_per_cpu_data() Eric Dumazet
2026-09-11 10:02 ` Hangbin Liu
2026-09-11 21:08 ` netdev-bot+sashiko
2026-09-12 14:46 ` Eric Dumazet
2026-09-16 1: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=178952100513.2346086.3291685247493878437.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.